A friend who has been LPing stablecoin pairs for years got curious about adding uniBTC to her strategy. She asked me how it would behave paired against WBTC on a DEX. I said probably similar to any other BTC-adjacent LP. I was half right. 🤔
She set up the pool. For the first week the ratios tracked reasonably. Then she started noticing drift. The pool wasn't moving cleanly with BTC price. The uniBTC side was accumulating value through exchange rate appreciation, but the AMM's pricing logic treated it as a static balance, not accounting for the silent yield accrual underneath. The pool rebalanced around token count rather than the real value each token represented at any given moment.
When she pointed that out, I understood something I had been treating as a technicality. Non-rebasing tokens don't just change how yield appears in your wallet. They change how automated market makers price the pair. The AMM sees stable token balances. The exchange rate is moving underneath those balances. Those two things interacting inside a liquidity pool create behavior that doesn't cleanly track either asset's spot price trajectory.
This doesn't make uniBTC bad for LPing. It makes it different in a specific technical way that most people running BTC liquidity strategies have never had to think about before. The impermanent loss calculation changes because the value relationship between the two tokens is not static. The rebalancing behavior changes. None of that complexity shows up in the APY display you see before you enter the pool.
Bedrock solved a real upstream composability problem by going non-rebasing. Every DeFi primitive that integrates uniBTC downstream inherits a version of that same design decision in a different form. Whether that costs or benefits you depends entirely on what you're doing with the token. My friend figured this out on a small position. Better that way. 😂
