For holders

Staking liquidity

What you put in, what you get back, and what can change in between.

Two ways to deposit

Method	What happens	When to use it
USDC only	The vault swaps half your USDC into the token, then adds both sides in one transaction.	You hold USDC and just want exposure to the fees.
Both sides	You supply USDC and the token yourself. Nothing is swapped.	You already hold the token, or the price band is blocking single-sided entry.

Either way, anything the position cannot absorb at the current ratio is refunded in the same transaction. You are never left with a stranded balance inside the vault.

Large single-sided deposits fill partially

The vault refuses to move the price further than its safety band allows. A USDC-only deposit worth a few percent of the pool's depth will hit that limit part-way through, deploy what it can, and refund the rest. In testing, a deposit worth around 2.5% of pool depth deployed about 81%; one worth 0.2% deployed 99.9%. Split large deposits, or use the two-sided method.

What your shares represent

Shares are a plain ERC-20. They are a claim on a fraction of the vault's Uniswap position — not a fixed amount of either token.

That means your balance shifts with the price, exactly as it would if you held the position yourself. If the token rises against USDC, your position ends up holding more USDC and less of the token. This is ordinary automated-market-maker behaviour, usually called impermanent loss, and it applies here in full. Slice does not hedge it.

Shares are transferable — sending them moves the underlying claim.
Your unclaimed rewards do not move with them. They stay with whoever earned them.
There is no lockup. Withdraw whenever you like.

Claiming

Rewards accrue in USDC, every second, based on how many shares you hold and how long you hold them. They sit in the vault until you call claim(); there is no deadline and no penalty for leaving them there.

Claiming is separate from withdrawing. You can take your rewards and stay staked, or withdraw your position and claim afterwards.

Withdrawing

Burning shares removes the matching slice of liquidity and returns both tokens. The vault harvests first, so any fees the position had accrued go to the stream rather than to whoever happens to withdraw next.

Withdrawals keep working even when the price oracle is cold or the market is moving violently. That was a deliberate design constraint, not an accident. More on that →

Reading the APR

The APR on the pools table annualises the current payout rate. It is a run-rate, not a realised return, and it is volatile by construction: it jumps after a busy hour and decays as the seven-day stream unwinds.

Treat it as a snapshot of recent trading activity, not a promise about the next year.

Your floor is written into the transaction

Every deposit and withdrawal carries a minimum. Before you sign, the app quotes what the call should return at the current price — shares on the way in, USDC and the token on the way out — and sends that figure less your slippage tolerance as the floor. If the pool moves between quoting and confirming so you would receive less, the transaction reverts and nothing is taken. The default tolerance is 0.5%; it is adjustable, and remembered per browser.

Approvals are for the exact amount you enter, not unlimited. A deposit can never move more than the maximum you typed, so an open-ended approval would buy nothing except exposure to any bug in an unaudited contract.