Top venue rate
+0.5000%
Bitunix · USDT
Detail view
RIF funding
Review RIF funding rates, settlement timing, and venue-by-venue snapshots from CoinCryptoRank's first-party funding feed across 8 exchanges.
8 pairs trackedscheduleexchangesverifiedFirst-party data
Venue coverage
8
Active RIF snapshots
Live market snapshot
RIF funding is positive at +0.0669%, but venues disagree: the +0.4950% spread between the highest and lowest funding rate across 8 exchanges is a live cross-exchange arbitrage window for neutral positions.
Highest
trending_up+0.5000%
Peak positive
Lowest
trending_down+0.0050%
Peak negative
Mean funding
equalizer+0.0669%
Composite
Current APY
percent+79.39%
Extrapolated from backend data.
Funding rate comparison
RIF — multi-exchange funding history
Compare historical funding rates across multiple exchanges. Each exchange is a separate line.
Exchanges (select 1–6)
14 exchanges available
Stats summary
Exchanges tracked
2
Data points
0
Best spread
--
Status
Ready
Fetching funding data...
Select exchanges above to compare funding rate history.
Funding rate by venue
Current RIF funding rate by exchange
Live funding rate and annualized APR for {symbol} perpetual contracts on each exchange — updated continuously from exchange data.
| Venue | Funding rate | Annualized APR | Settlement frequency | Next apply |
|---|---|---|---|---|
| BitunixUSDT | ▲+0.5000% | +547.50% | Every 8h | scheduleOct 04, 20:00 UTC |
| AsterUSDT | ▲+0.0050% | +43.80% | Every 1h | scheduleOct 04, 20:00 UTC |
| BinanceUSDT | ▲+0.0050% | +5.48% | Every 8h | scheduleOct 04, 20:00 UTC |
| BingxUSDT | ▲+0.0050% | +10.95% | Every 4h | scheduleOct 04, 20:00 UTC |
| GateUSDT | ▲+0.0050% | +5.48% | Every 8h | scheduleJan 01, 00:00 UTC |
| KucoinUSDT | ▲+0.0050% | +5.48% | Every 8h | scheduleOct 04, 20:00 UTC |
| MexcUSDT | ▲+0.0050% | +10.95% | Every 4h | scheduleOct 04, 16:00 UTC |
| PionexUSDT | ▲+0.0050% | +5.48% | Every 8h | scheduleOct 04, 20:00 UTC |
Venue breakdown
0 funding records found for RIF.
finance
No funding records for RIF yet.
The backend snapshot may still be refreshing.