Every swap
pays every staker.

From swaps, not transfers. $RFS is a plain ERC-20 with no tax in it at all. The fee is levied by a Uniswap v4 hook attached to the ETH/$RFS pool: it takes 5% of every swap in that pool, always denominated in $RFS, and splits it 2% to stakers / 2% burned / 1% to the treasury. Those shares are constants in the contract — nobody can change them.

No — you stake. Paying holders by rebasing their balances means burying reflection accounting inside the token itself, which routers, launchpads and Uniswap v4 all refuse to handle properly. So the 2% goes to a staking vault instead, split pro-rata between everyone staking. It costs you one approval and one stake transaction, and in exchange what you are owed is an explicit number you can read on-chain rather than a rebase you have to trust.

No. Sending $RFS to a friend, to a cold wallet or into the staking vault costs nothing beyond gas. The only place the fee applies is a swap inside the hooked pool.

The hook accrues them as ERC-6909 claims inside the PoolManager — a balance write rather than a token transfer, so the swap path stays cheap. Anyone can then call distribute(), which redeems the claims in bulk and pushes out all three slices at once: the staking share lands in the vault, where sync() folds it into the reward accumulator. The stake page shows how much is waiting and lets you push it yourself.

It ranks stakers by what they currently hold in the vault, ties going to whoever staked first, and every input is public chain state: Staked logs for who has ever staked, userInfo for what each of them holds, totalStaked for the denominator. There is no backend and nothing we report — anyone can recompute the same board from an RPC endpoint and check it against ours. Splitting a balance across wallets only moves you down it. What the contracts do not enforce is the payout: the 1% lands in a treasury address fixed at deployment, and sending it out at the end of an epoch is a human decision. The wallet is public, so you can verify it happened.

In principle, yes, and we would rather say so than pretend otherwise. A PoolKey includes the hook address, so a v2 or v3 pool — or a v4 pool with no hook — on the same pair is permissionless and untaxed. Robinhood Chain has all three deployed. Nothing in the hook can prevent that; concentrating liquidity in the hooked pool is what makes the fee bite.

Through pools.trade, the front-end for Uniswap's own LiquidityLauncher on Robinhood Chain, as a liquidity bootstrapping auction. When the auction settles, the strategy initializes the ETH/$RFS v4 pool at the clearing price with our hook attached. Only that strategy can initialize a pool carrying the hook, so exactly one pool can ever exist — and nobody could front-run it into existence at a price of their choosing. Auction volume is untaxed; the 5% starts at listing.

None. Unstake any amount at any time, and it claims your pending rewards in the same transaction. There is also an emergencyWithdraw() that returns your principal while forfeiting pending rewards — it deliberately touches no reward accounting, so it stays callable even in the worst case.

The token, the vault and the hook are published here and in the docs at launch, and linked to Blockscout from the stake page. Until then, treat any circulating address as fake.