rsETH supply on Ethereum
rsETHrsETH totalSupply() on Ethereum at the day's last block, including the rsETH held in escrow for other chains.
Is every rsETH on every chain backed, and how long does an rsETH withdrawal take?
What backs Kelp's rsETH, how its supply is spread across chains, the escrow behind bridged rsETH and how withdrawals are paid.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
What stands behind rsETH, its price and the withdrawals waiting.
rsETH totalSupply() on Ethereum at the day's last block, including the rsETH held in escrow for other chains.
The rsETH to ETH price set by Kelp's LRT oracle at its latest update.
ETH, ETHx and stETH in the deposit pool, node delegators, EigenLayer and withdrawals in progress, valued in ETH at each token's own rate.
rsETH locked in withdrawal requests that have not been claimed, at the latest block.
The assets behind rsETH by kind: native ETH in validators, liquid staking tokens in EigenLayer strategies and assets waiting in Kelp's contracts.
rsETH's oracle price by day beside its price in its main DEX pools.
rsETH on other chains, the escrow that backs it and every bridge message.
rsETH locked in the bridge adapter on Ethereum that backs rsETH minted on other chains, at the latest block.
The sum of rsETH totalSupply on every other chain at each chain's day-end block.
rsETH supply on other chains beside the escrow that backs it, by day, so a gap shows the day it opens.
Each rsETH send and receive on the bridge adapter with its source and destination chains, amount, verifier setting and transaction.
Kelp issues rsETH against ETH and liquid staking tokens that it restakes through EigenLayer, at a price its oracle sets from the assets it holds. This dashboard reads Kelp's contracts to show what stands behind rsETH, how its supply is spread between Ethereum and other chains and how quickly withdrawals are paid.
rsETH on other chains is backed by rsETH held in escrow by a bridge adapter on Ethereum. In April 2026 an attacker forged a cross-chain message to that adapter and had rsETH released from the escrow, leaving rsETH elsewhere short of backing; Kelp paused the token, and the escrow was refilled in May under a recovery plan funded by several protocols. The dashboard compares escrow with supply every day, so a gap like that one shows the day it opens.
Every mint and release on the bridge is listed with its transaction and the number of verifiers its route required. Each figure opens a receipt with its block and the contract read behind it.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →Read from chain state and history
rsETH is Kelp's liquid restaking token. Kelp takes ETH and liquid staking tokens such as ETHx and stETH, restakes them through EigenLayer and issues rsETH at a price set by its oracle, which rises as rewards accrue.
In April 2026 an attacker forged a cross-chain message to the adapter that holds rsETH in escrow for other chains, and rsETH was released from it. rsETH on other chains lacked full backing until the escrow was refilled in May 2026 through a recovery plan funded by several protocols. The dashboard keeps escrow and supply by chain from before the attack onward.
Compare the rsETH supply on that chain with the rsETH locked for it in the adapter on Ethereum at the same time. The escrow chart does this daily, and the bridge table lists every mint and release with its transaction.
A withdrawal request locks rsETH and names the asset to receive. Kelp unlocks the request once assets come back from EigenLayer and its delay has passed, and the holder then claims. The dashboard shows rsETH waiting and how long recent requests took.
A cross-chain message is only as safe as the verifiers that must approve it. A route that relies on a single verifier fails if that verifier is misled or compromised, which is what the April 2026 attack exploited. The bridge table shows how many verifiers each rsETH route required when each message passed.
Whether weETH, rsETH, ezETH and other liquid restaking tokens hold the assets they claim, where that backing sits and how rates moved.
EthereumArbitrumBase+1Each major LayerZero-bridged token, route by route: which verifiers check its messages, how many must agree and whether one alone suffices.
Multi-chainEthereumArbitrum+5Whether each bridged token's supply on other chains is matched by tokens locked on its home chain, with every gap shown.
Multi-chainEthereumBase+4Assets restaked on EigenLayer by strategy, the operators they are delegated to, the AVSs those operators secure and each slashing event.
EthereumA dated report on restaking in 2026: what left EigenLayer and where it went, the shifts in liquid restaking tokens, slashing and rewards.
EthereumETH staked on the beacon chain, its share of total supply, active validators and the deposits and exits that move it, epoch by epoch.
EthereumStart free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.