SOL/cbBTC pool timelapse

Day-by-day replay of a Kamino + Meteora pool ladder over any date range of the past year: every borrow, pool opening, range exit, close, swap and repayment, with the Kamino loan balances and each pool's token mix.

Live
Live LTV
Live collateral
Open pools
Live drawdown
Period totals
Total fee profit
Max LTV
Max collateral in Kamino
Max drawdown
Average debt
Average collateral
Ratio (SOL per cbBTC) and pool ranges
Pool in rangePool out of rangeRatio
Net result (cbBTC, fees included)
Meteora pools
#RangeStatusMix SOL / cbBTCSOLcbBTCFees (USDC)Debt SOLDebt cbBTCPool P/L
Kamino transactions
Meteora pools and swaps

Model: Meteora pools behave as concentrated-liquidity ranges (spot shape). Fees accrue only while the ratio is inside a pool, at the daily rate you set, paid half in SOL and half in cbBTC, and are claimed when the pool closes. The USDC fee figure values all fee tokens earned so far at the day's prices; fee yield divides it by the peak amount borrowed. Live LTV, live collateral and live drawdown show the current playback day; live drawdown is how far the strategy result is below its highest point so far. Drawdown % is that dollar drop divided by the amount borrowed (the capital working in pools) on that day. The other dashboard values are up to the current playback day, with the full-period figure alongside while playing. Max LTV includes the moment inside a day before a top-up fires; max drawdown is the largest drop of the strategy result (pools, fees and closed pools, in dollars) from its previous high, excluding SOL price changes on wallet and collateral. Interest accrues in tokens on each pool's Kamino loans. When the Kamino LTV goes above your top-up level, SOL is deposited as extra collateral to bring it back to the target; that SOL is your own money, so it is counted separately and not as profit or loss. Once a day, if the LTV is below your withdraw level, there is debt and the excess is at least $20, the excess collateral goes to your wallet to bring the LTV up to that level, taking SOL first, then cbBTC, then USDC. Top-ups use SOL from the wallet before any new money. Wallet total value includes SOL price changes, so it differs from the pool result. Your wallet sits between Kamino and Meteora: borrowed tokens land in the wallet and go from there into a pool; a closed pool's tokens and fees come back to the wallet, and loans are repaid from the wallet. The bot never swaps: each loan is repaid with the same token, anything left over stays in the wallet as profit, and if the wallet holds less of a token than a loan needs, the rest of that loan stays open and is repaid as soon as the wallet has that token. The pool result is still shown in cbBTC at the day's ratio. When the price leaves every pool, the bot opens a new one at the current price. With no pool limit (the default) it never sells SOL: it borrows more cbBTC for each new pool and every pool waits for the price to come back. If you set a limit, the bot closes the pool farthest from the price to make room. In one-sided cbBTC mode, while the ratio falls back through a pool, the bot withdraws the cbBTC that comes back every hour and repays that part of the loan straight away, so the pool shrinks and the debt goes down smoothly with the price (you can switch this off). A pool that the ratio falls below is all cbBTC again, so the bot closes it, repays the rest of its loan and keeps the fees. The bot opens a new pool when the ratio rises above every pool (SOL getting weaker), or when it falls a full range width (e.g. 1.68%) below the last pool, but never below the floor ratio you set (default 835, today's price). If the start date's ratio is below the floor, the first pool waits until the ratio reaches it. BTC stands in for cbBTC; synthetic paths hold BTC at $76,820. The real path runs on hourly Binance closes (SOLUSDT and BTCUSDT, 3 Nov 2025 00:00 to 3 Nov 2026 16:00 UTC), so the bot acts every hour; the round-trip paths are interpolated hourly. Log times (UTC) are the hour in which each action happened; end-of-day checks show 00:00 of the next day. Moves inside an hour are not captured.