Perp Market Week 35, 2026: Volume, Funding, Costs
PerpFinder Research · Published
In ISO week 35 of 2026, the stored daily snapshots hold $1,476.96 billion of centralized perpetual volume. The perp-DEX protocols hold $158.87 billion over the same days, a share of 9.71 percent. The open-interest-weighted BTC funding rate held a median of 0.000796 percent per hour, or 6.98 percent at a simple annual rate. A $1,000,000 BTC perpetual order cost a median of 6.464 basis points across 926 order-book observations.
Measurements of stored PerpFinder data, never accusations. A weekly figure is the sum of stored daily snapshots and not an exact calendar week. A venue-day that the spike rule holds out stays visible in the spike table. This report does not claim that any venue misreports volume.
What this report measures
PerpFinder collects four stored series of the perpetual market. The daily snapshot series stores the reported 24-hour volume of each venue once a day. The funding sweep stores the rate of each venue every 15 minutes. The execution-cost sweep walks the order book of each venue every 6 hours. This report reads those stored series for ISO week 35 of 2026, which runs from 2026-08-24 to 2026-08-30.
Each weekly volume figure is the sum of 7 stored daily snapshots. A snapshot covers the 24 hours before its own capture instant. The sum therefore measures 7 stored days, and it does not measure an exact calendar week. Each table on this page states its own measurement instant, because the collection clocks are different.
The generator reads only stored PerpFinder data. It fetches no venue endpoint at build time, and it writes no value that the stored series does not hold. The methodology of each series is on the research hub.
Volume in week 35 against week 34
The centralized venues stored $1,476.96 billion of perpetual volume across the 7 days of 2026-W35. The perp-DEX protocols stored $158.87 billion across the same 7 days. Both figures apply the spike rule. That rule holds a venue-day above 3 times the 7-day median of the same venue out of the total.
The stored total of 2026-W34 is $1,438.33 billion. That week does not sit on the same basis. The snapshot series reconstructed 6 of its 7 stored days after the fact, from the 00:00 UTC volume-quality sweep. Each reconstructed day carries fewer venues. A comparison of the two headline totals therefore compares two different venue sets.
The comparable set holds the 20 venues that both weeks store on every day. On that set the centralized total moved from $1,402.13 billion to $1,356.30 billion, a change of -3.3 percent. The set leaves out Backpack, BitMEX, WEEX, because 2026-W34 does not store those venues on every day.
Measured perpetual volume per stored day, 2026-W35
Measured at 2026-08-24 00:00 UTC to 2026-08-30 23:59 UTC — one stored snapshot per day, capture time in the second column · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history
Each row is one stored daily snapshot. The centralized figure sums the venues of that day after the spike rule. The perp-DEX figure is the stored daily total across the protocols with a positive figure. A day that stores no perp-DEX row keeps a null cell. Download this table as CSV
| Date | Capture (UTC) | CEX venues | CEX volume ($B) | DEX volume ($B) | DEX protocols | DEX share (%) | Spike-flagged venue-days |
|---|---|---|---|---|---|---|---|
| 2026-08-24 | 13:10 | 23 | 239.21 | 18.63 | 89 | 7.22 | 0 |
| 2026-08-25 | 13:07 | 23 | 310.5 | 30.76 | 86 | 9.01 | 0 |
| 2026-08-26 | 13:12 | 23 | 218.79 | 29.19 | 87 | 11.77 | 0 |
| 2026-08-27 | 22:13 | 23 | 246.99 | 22.7 | 87 | 8.42 | 0 |
| 2026-08-28 | 22:14 | 23 | 259.1 | 25.56 | 86 | 8.98 | 0 |
| 2026-08-29 | 16:40 | 23 | 107.91 | 23.53 | 87 | 17.9 | 0 |
| 2026-08-30 | 16:37 | 23 | 94.47 | 8.5 | 86 | 8.26 | 0 |
Scroll the columns sideways to see every field. The CSV holds the same rows.
The spike rule and the venue-days it held out
PerpFinder flags a venue-day when the venue reports more than 3 times the median of its own previous 7 stored days. A flagged venue stays visible on the site and leaves the headline total until the figure holds. The rule needs at least 3 stored days behind the median.
No venue-day of 2026-W35 passed the rule, so the weekly total of 2026-W35 holds every stored venue-day. The rule flagged 21 venue-days of 2026-W34, and the spike table names each one.
The flagged venue-days of 2026-W34 fall on the reconstructed days. A reconstructed day reads the 00:00 UTC sweep, and the captured days read a later instant, so the two measurements sit on different clocks. The multiple measures that basis change as much as it measures a market move.
Venue-days that the spike rule held out of the 2026-W34 total
Measured at 2026-08-17 00:00 UTC to 2026-08-23 23:59 UTC — stored daily snapshots · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history
A venue-day enters this table when the venue reported more than 3 times the median of its own previous seven stored days. The venue-day stays visible and leaves the headline total. The baseline column counts the stored days behind the median. Download this table as CSV
| Venue | Date | Reported 24h ($B) | 7-day median ($B) | Multiple | Baseline days |
|---|---|---|---|---|---|
| Deribit | 2026-08-20 | 1.26 | 0.23 | 5.4 | 7 |
| Bitmart | 2026-08-20 | 25.87 | 4.99 | 5.2 | 7 |
| Kraken | 2026-08-20 | 1.78 | 0.46 | 3.8 | 7 |
| BloFin | 2026-08-20 | 1.72 | 0.55 | 3.1 | 7 |
| KuCoin | 2026-08-20 | 3.31 | 1.07 | 3.1 | 7 |
| Bybit | 2026-08-20 | 25.24 | 8.2 | 3.1 | 7 |
| HTX | 2026-08-20 | 3.29 | 1.07 | 3.1 | 7 |
| Deribit | 2026-08-21 | 1.43 | 0.23 | 6.2 | 7 |
| Kraken | 2026-08-21 | 1.77 | 0.46 | 3.8 | 7 |
| Bitmart | 2026-08-21 | 16.15 | 4.99 | 3.2 | 7 |
| Deribit | 2026-08-22 | 2.13 | 0.27 | 8 | 7 |
| Bitmart | 2026-08-22 | 34.35 | 4.99 | 6.9 | 7 |
| Kraken | 2026-08-22 | 3.02 | 0.46 | 6.5 | 7 |
| KuCoin | 2026-08-22 | 4.32 | 1.07 | 4 | 7 |
| BloFin | 2026-08-22 | 2.09 | 0.56 | 3.7 | 7 |
| Crypto.com | 2026-08-22 | 1.16 | 0.33 | 3.5 | 7 |
| Bybit | 2026-08-22 | 28.65 | 8.2 | 3.5 | 7 |
| XT.COM | 2026-08-22 | 15.75 | 4.78 | 3.3 | 7 |
| HTX | 2026-08-22 | 3.66 | 1.17 | 3.1 | 7 |
| OKX | 2026-08-22 | 51.51 | 16.82 | 3.1 | 7 |
| Bitget | 2026-08-22 | 18.63 | 6.09 | 3.1 | 7 |
Scroll the columns sideways to see every field. The CSV holds the same rows.
Venue ranks and the moves inside them
The comparable set puts five venues at the top of 2026-W35. The list is Binance at $389.76 billion, OKX at $158.48 billion, Toobit at $130.53 billion, Bybit at $95.59 billion, MEXC at $88.03 billion.
The rank table counts the venue-days that entered each weekly figure. The spike rule took 21 venue-days out of 2026-W34, so a venue with a lower day count also carries a lower weekly figure. A move that pairs with a different day count is partly a coverage effect.
Among the venues with 7 counted days in both weeks, the largest move belongs to Bitunix, from rank 8 to rank 12.
Venue rank and weekly volume, 2026-W35 against 2026-W34
Measured at 2026-08-24 00:00 UTC to 2026-08-30 23:59 UTC and 2026-08-17 00:00 UTC to 2026-08-23 23:59 UTC · PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history
The table holds the venues that both weeks store on every day. The days column counts the venue-days that entered each weekly figure, so a venue that lost a day to the spike rule shows a lower count and a lower figure. A rank move with different day counts is partly a coverage effect. Download this table as CSV
| Venue | Rank 2026-W35 | Rank 2026-W34 | Move | 2026-W35 ($B) | 2026-W34 ($B) | Days 2026-W35 | Days 2026-W34 |
|---|---|---|---|---|---|---|---|
| Binance | 1 | 1 | 0 | 389.76 | 464.8 | 7 | 7 |
| OKX | 2 | 2 | 0 | 158.48 | 144.86 | 7 | 6 |
| Toobit | 3 | 3 | 0 | 130.53 | 139.79 | 7 | 7 |
| Bybit | 4 | 9 | +5 | 95.59 | 55.63 | 7 | 5 |
| MEXC | 5 | 4 | -1 | 88.03 | 139.29 | 7 | 7 |
| Gate.io | 6 | 5 | -1 | 70.63 | 84.55 | 7 | 7 |
| Bitmart | 7 | 13 | +6 | 66.13 | 21.66 | 7 | 4 |
| Bitget | 8 | 10 | +2 | 59.54 | 51.02 | 7 | 6 |
| WhiteBIT | 9 | 6 | -3 | 57.53 | 65.9 | 7 | 7 |
| Coinbase | 10 | 7 | -3 | 52.11 | 58.97 | 7 | 7 |
| XT.COM | 11 | 12 | +1 | 50.77 | 43.11 | 7 | 6 |
| Bitunix | 12 | 8 | -4 | 46.31 | 56.15 | 7 | 7 |
| BingX | 13 | 11 | -2 | 40.54 | 46.81 | 7 | 7 |
| KuCoin | 14 | 14 | 0 | 13.06 | 7.74 | 7 | 5 |
| HTX | 15 | 15 | 0 | 10.34 | 6.73 | 7 | 5 |
| Kraken | 16 | 19 | +3 | 6.76 | 2.39 | 7 | 4 |
| BloFin | 17 | 17 | 0 | 5.9 | 3.61 | 7 | 5 |
| Phemex | 18 | 16 | -2 | 5.03 | 4.85 | 7 | 7 |
| Deribit | 19 | 20 | +1 | 4.96 | 1.04 | 7 | 4 |
| Crypto.com | 20 | 18 | -2 | 4.29 | 3.25 | 7 | 6 |
Scroll the columns sideways to see every field. The CSV holds the same rows.
BTC funding: level and cross-venue spread
The open-interest-weighted BTC funding rate held a median of 0.000796 percent per hour across the 672 sweeps of 2026-W35. At a simple annual rate that median is 6.98 percent. The median stayed positive, so a long paid the short over the week on the weighted average of the venues.
The cross-venue spread is the highest venue rate minus the lowest venue rate in one sweep. Its median over the week is 0.00320 percentage points per hour. The widest single sweep of the week is 2026-08-25 06:30 UTC, at 0.01735 percentage points per hour. In that sweep 26 venues published a rate, between -0.00035 percent and 0.01700 percent per hour.
The week stored 672 of the 672 sweeps that a full week holds at this cadence. Venue coverage stayed between 25 and 27 venues per sweep.
BTC funding level and cross-venue spread per day, 2026-W35
Measured at 2026-08-24 00:00 UTC to 2026-08-30 23:59 UTC — 672 sweeps at a 15-minute cadence · PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates
The open-interest-weighted rate weights each venue by its own open interest in the same sweep. The spread is the highest venue rate minus the lowest venue rate in one sweep. All figures are percent per hour. Download this table as CSV
| Date | Sweeps | OI-weighted median (%/h) | Median spread (pp/h) | Widest spread (pp/h) |
|---|---|---|---|---|
| 2026-08-24 | 96 | 0.001246 | 0.00329 | 0.00561 |
| 2026-08-25 | 96 | 0.000817 | 0.0037 | 0.01735 |
| 2026-08-26 | 96 | 0.000581 | 0.00254 | 0.00536 |
| 2026-08-27 | 96 | 0.000496 | 0.00359 | 0.00638 |
| 2026-08-28 | 96 | 0.000906 | 0.00301 | 0.00446 |
| 2026-08-29 | 96 | 0.000889 | 0.00298 | 0.00449 |
| 2026-08-30 | 96 | 0.000774 | 0.00254 | 0.00351 |
Realized funding, venue by venue
The realized ledger stores each settlement that a venue published. For 2026-W35 it holds 420 settlements from 6 venues, and every one of those venues published a complete week.
A long position paid the most on Hyperliquid, at 0.2182 percent of the position over the week. A long paid the least on dYdX, at -0.0068 percent of the position over the week. A negative figure means a long received funding instead of paying it.
The settlement interval differs between venues, so the realized table states the interval of each venue in minutes. A venue with a shorter interval writes more rows into the ledger. The weekly sum stays comparable between venues, because each sum covers the same period.
Realized BTC funding paid by a long, 2026-W35
Measured at 2026-08-24 00:00 UTC to 2026-08-30 23:59 UTC — 420 stored settlements · PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized
The value is the sum of the settlement rates that the venue published inside the week. A positive figure means a long paid. The ledger covers the venues that publish a settlement history, so it does not describe the whole market. Download this table as CSV
| Venue | Paid over the week (%) | Settlements | Expected | Interval (min) |
|---|---|---|---|---|
| Hyperliquid | 0.2182 | 168 | 168 | 60 |
| Binance | 0.1753 | 21 | 21 | 480 |
| OKX | 0.1388 | 21 | 21 | 480 |
| Bybit | 0.1157 | 21 | 21 | 480 |
| Gate.io | 0.0704 | 21 | 21 | 480 |
| dYdX | -0.0068 | 168 | 168 | 60 |
Execution cost of a $1,000,000 BTC perpetual order
The cost engine walks the order book of each venue every 6 hours and records the total cost of a $1,000,000 BTC perpetual order. Total cost is the taker fee plus the half-spread plus the size-dependent impact beyond the best quote. Across the 28 stored sweeps of 2026-W35 the median of the 926 order-book observations is 6.464 basis points.
The set of 28 order-book venues filled the order in every stored sweep of the week. The three lowest weekly medians in that set are Lighter at 1.571 basis points, MEXC at 2.024 basis points, Extended at 3.173 basis points. Each figure is the median of the sweeps of that venue. The cost table states the lowest sweep and the highest sweep of each venue.
An oracle venue has no order book, so it is not in these numbers. The walk found 12 venues that could not fill the order in at least one sweep, and a sweep without a fill contributes no cost figure. The week uses cost methodology version 4, which is the version the store held for the whole week.
Total execution cost of a $1,000,000 BTC perpetual order, 2026-W35
Measured at 2026-08-24 00:56 UTC to 2026-08-30 18:56 UTC — 28 sweeps, cost methodology version 4 · PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history
Total cost is the taker fee plus the half-spread plus the size-dependent impact beyond the best quote. Order-book venues only; an oracle venue has no book and does not appear. The sweeps column counts the sweeps in which the venue filled the order. Download this table as CSV
| Venue | Type | Median total (bps) | Lowest (bps) | Highest (bps) | Sweeps |
|---|---|---|---|---|---|
| Lighter | dex | 1.571 | 0.886 | 11.482 | 28 |
| MEXC | cex | 2.024 | 2.006 | 2.381 | 28 |
| Extended | dex | 3.173 | 2.563 | 4.428 | 28 |
| Coinbase | cex | 4.597 | 4.199 | 5.434 | 28 |
| Aster | dex | 4.633 | 3.812 | 6.48 | 28 |
| Hyperliquid | dex | 5.027 | 4.562 | 6.715 | 27 |
| NADO | dex | 5.205 | 4.49 | 6.333 | 28 |
| GRVT | dex | 5.221 | 4.646 | 9.004 | 28 |
| BingX | cex | 5.355 | 5.032 | 5.874 | 28 |
| Binance | cex | 5.63 | 5.006 | 6.292 | 28 |
| OKX | cex | 5.711 | 5.012 | 6.944 | 28 |
| Toobit | cex | 6.006 | 6.006 | 6.772 | 28 |
| Bitmart | cex | 6.009 | 6.006 | 6.814 | 28 |
| XT.COM | cex | 6.025 | 6.019 | 6.559 | 28 |
| Bitunix | cex | 6.044 | 6.034 | 6.064 | 28 |
| BloFin | cex | 6.262 | 6.006 | 6.493 | 28 |
| Gate.io | cex | 6.367 | 5.465 | 7.47 | 28 |
| Bybit | cex | 6.658 | 5.743 | 7.434 | 28 |
| Bitget | cex | 6.734 | 6.007 | 7.698 | 28 |
| Kraken | cex | 7.139 | 6.318 | 8.438 | 28 |
| HTX | cex | 7.206 | 6.242 | 9.219 | 28 |
| Deribit | cex | 7.898 | 3.796 | 10.44 | 28 |
| KuCoin | cex | 8.091 | 7.236 | 8.837 | 28 |
| Phemex | cex | 8.299 | 6.935 | 10.246 | 27 |
| StandX | dex | 8.363 | 7.35 | 9.802 | 28 |
| SunX | dex | 9.161 | 7.241 | 12.419 | 23 |
| Apex Omni | dex | 9.162 | 5.173 | 22.63 | 28 |
| Crypto.com | cex | 10.456 | 9.611 | 13.171 | 28 |
| RISEx | dex | 11.514 | 10.418 | 14.799 | 28 |
| Aevo | dex | 12.793 | 10.736 | 26.045 | 26 |
| WhiteBIT | cex | 13.328 | 11.592 | 15.091 | 28 |
| dYdX | dex | 16.522 | 10.4 | 69.163 | 28 |
| Ondo | dex | 21.873 | 19.328 | 22.926 | 13 |
| Hibachi | dex | 24.898 | 16.424 | 42.644 | 26 |
Scroll the columns sideways to see every field. The CSV holds the same rows.
What this week rests on
The volume figures rest on 7 stored days, 23 centralized venues per day and between 86 and 89 perp-DEX protocols with a positive figure. The funding figures rest on 672 sweeps and 420 stored settlements. The execution-cost figures rest on 28 sweeps and 926 order-book observations. The volume-quality series adds 28 sweeps of 20 venues inside the same week.
The week carries the gaps named here.
The snapshot series reconstructed 6 of the 7 stored days of 2026-W34 from the 00:00 UTC volume-quality sweep. That week therefore carries fewer venues and a different read instant.
The snapshot series stores a perp-DEX total on 1 of the 7 days of 2026-W34, so no perp-DEX comparison between the two weeks exists.
The comparable venue set leaves out Backpack, BitMEX, WEEX, because 2026-W34 does not store those venues on every day.
The spike rule held 21 venue-days out of the 2026-W34 total.
The cost series carries fewer than 28 sweeps for 6 order-book venues, so the weekly median of those venues rests on a shorter series.
The active cost methodology is now version 5, and this week is stored under version 4. The two versions are never merged.
Limitations
Reported volume comes from the ticker endpoint of each venue. PerpFinder normalizes the unit and the market type, and does not audit the venue figure.
A daily snapshot is one reading per day. A venue that moved inside the day, or that published a different figure at another hour, produces a different weekly sum on another clock.
The funding sweep and the cost sweep each read one instant. Depth and rates change between readings, and a later reading returns different numbers.
The realized ledger covers the venues that publish a settlement history. It does not describe the venues that publish none.
How to reproduce these numbers
Every number comes from public endpoints that need no key. The funding figures come from https://perpfinder.com/api/data/funding-history?asset=BTC&type=aggregates&days=30 and from the same endpoint with type=realized. The execution-cost figures come from https://perpfinder.com/api/data/cost-history?market=perp&asset=BTC&size=1000000&days=all. The volume figures come from https://perpfinder.com/api/data/venue-history?venue=Binance&days=30 and the same endpoint for each venue.
Those endpoints serve the current state, so a later call returns later numbers. Each table on this page carries a CSV with the exact rows of 2026-W35, and the fact block carries a CSV of every headline figure.
Collection cadence and updates
The collection cadence is fixed. The funding sweep runs every 15 minutes, the execution-cost sweep and the volume-quality sweep run every 6 hours, and the venue snapshot runs each day.
PerpFinder keeps no fixed publication schedule for this series. A published report is not edited after publication, and a later week is published as a new page.
The numbers
| Metric | Value |
|---|---|
| Centralized perpetual volume, 2026-W35 (USD billion, sum of 7 stored daily snapshots, spike rule applied)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 1,476.96 |
| Centralized perpetual volume, 2026-W34 (USD billion, sum of 7 stored daily snapshots, spike rule applied)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 1,438.33 |
| Centralized perpetual volume, 2026-W35, venues stored on every day of both weeks (USD billion)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 1,356.3 |
| Centralized perpetual volume, 2026-W34, venues stored on every day of both weeks (USD billion)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 1,402.13 |
| Week-over-week change of centralized perpetual volume on the comparable venue set (percent)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | -3.3 |
| Centralized venues with a stored 24-hour figure on every day of 2026-W35PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 23 |
| Perp-DEX volume, 2026-W35 (USD billion, sum of 7 stored daily snapshots)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 158.87 |
| Days of 2026-W34 that store a perp-DEX totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 1 |
| Perp-DEX share of measured perpetual volume, 2026-W35 (percent)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 9.71 |
| Stored daily snapshots inside 2026-W35PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 7 |
| Window that one stored daily snapshot covers, counted back from its own capture instant (hours)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 24 |
| Centralized venues that both 2026-W35 and 2026-W34 store on every dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 20 |
| Fewest perp-DEX protocols with a positive figure on one day of 2026-W35PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 86 |
| Most perp-DEX protocols with a positive figure on one day of 2026-W35PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 89 |
| Spike rule: a venue-day above this multiple of the venue own 7-day median leaves the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 3 |
| Stored days that the spike-rule median looks back overPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 7 |
| Stored days the spike rule needs behind a median before it judges a venue-dayPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 3 |
| Venue-days of 2026-W35 that the spike rule held out of the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 0 |
| Venue-days of 2026-W34 that the spike rule held out of the headline totalPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 21 |
| Days of 2026-W34 that were reconstructed after the fact instead of capturedPerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 6 |
| Binance perpetual volume, 2026-W35 (USD billion, rank 1 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 389.76 |
| OKX perpetual volume, 2026-W35 (USD billion, rank 2 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 158.48 |
| Toobit perpetual volume, 2026-W35 (USD billion, rank 3 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 130.53 |
| Bybit perpetual volume, 2026-W35 (USD billion, rank 4 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 95.59 |
| MEXC perpetual volume, 2026-W35 (USD billion, rank 5 of the comparable venue set)PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history | 88.03 |
| BTC open-interest-weighted funding rate, median of 672 sweeps (percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 0.0008 |
| BTC open-interest-weighted funding rate, weekly median at an annual rate (percent, simple, 24 hours by 365 days)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 6.98 |
| BTC cross-venue funding spread, median of the sweeps (percentage points per hour, highest venue minus lowest venue)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 0.0032 |
| BTC cross-venue funding spread, widest single sweep of the week (2026-08-25 06:30 UTC, percentage points per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 0.0174 |
| Lowest venue funding rate in the widest sweep (2026-08-25 06:30 UTC, percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | -0.0004 |
| Highest venue funding rate in the widest sweep (2026-08-25 06:30 UTC, percent per hour)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 0.017 |
| Venues that published a BTC rate in the widest sweep (2026-08-25 06:30 UTC)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 26 |
| Stored BTC funding sweeps inside 2026-W35PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 672 |
| Cadence of the funding sweep (minutes)PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 15 |
| Fewest venues with a BTC rate in one sweep of 2026-W35PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 25 |
| Most venues with a BTC rate in one sweep of 2026-W35PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 27 |
| Sweeps a full week holds at the 15-minute cadencePerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates | 672 |
| Realized BTC funding paid by a long over 2026-W35, highest venue (Hyperliquid, percent of position)PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized | 0.2182 |
| Realized BTC funding paid by a long over 2026-W35, lowest venue (dYdX, percent of position)PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized | -0.0068 |
| Stored BTC funding settlements inside 2026-W35, all venues in the ledgerPerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized | 420 |
| Venues that published a complete week of BTC settlements to the ledgerPerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized | 6 |
| Order size of the execution-cost measurement, BTC perpetual (USD)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 1,000,000 |
| Total execution cost of a $1,000,000 BTC perpetual order, median of every order-book observation in 2026-W35 (basis points)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 6.464 |
| Order-book cost observations inside 2026-W35PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 926 |
| Stored execution-cost sweeps inside 2026-W35PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 28 |
| Cadence of the execution-cost sweep (hours)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 6 |
| Order-book venues with a cost figure in every stored sweep of 2026-W35PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 28 |
| Order-book venues with a cost figure in some but not every stored sweep of 2026-W35PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 6 |
| Venues that could not fill the $1,000,000 order in at least one stored sweep of 2026-W35PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 12 |
| Cost methodology version that the store treats as active at the time of the reportPerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 5 |
| Lighter total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 1)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 1.571 |
| MEXC total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 2)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 2.024 |
| Extended total execution cost of a $1,000,000 BTC perpetual order, weekly median (basis points, rank 3)PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history | 3.173 |
| Stored volume-quality sweeps inside 2026-W35PerpFinder volume-quality sweeps — /api/data/volume-quality-history | 28 |
| Venues in each stored volume-quality sweep of 2026-W35PerpFinder volume-quality sweeps — /api/data/volume-quality-history | 20 |
3 metrics suppressed (below sample thresholds — we publish gaps, not guesses)
volume.dex.week_over_week_change_pct— 2026-W34 stores a perp-DEX total on 1 of its 7 daysvolume.dex.prior_week_share_pct— 2026-W34 stores no perp-DEX total for 6 of its daysvolume.cex.headline_change_pct— the two weeks store different venue sets; the comparable-set change over 20 venues is published instead
Author: PerpFinder Research — the PerpFinder data desk. Published research carries the desk byline. Send a correction through the corrections page.
Sources: PerpFinder daily venue snapshots (data/history, venue-reported perpetual volume) — /api/data/venue-history · PerpFinder funding sweeps, BTC aggregates — /api/data/funding-history?asset=BTC&type=aggregates · PerpFinder realized-funding ledger, BTC — /api/data/funding-history?asset=BTC&type=realized · PerpFinder execution-cost history, BTC, $1,000,000 order — /api/data/cost-history · PerpFinder volume-quality sweeps — /api/data/volume-quality-history
Facts are generated deterministically from PerpFinder’s self-collected datasets (frozen methodology, versioned for each reported series) and are never edited by hand — only the narrative around them is editorial. Republishing the numbers is welcome with attribution: data license.