Kelpdao availability is defined by Ethereum and selected L2 routes

Avoiding obsolete network lists before moving rsETH

Obsolete chain lists are the most common cause of choosing an rsETH route Kelp no longer services.

A deployment proves code exists, not that minting, bridging, or recovery remains open. Match three identifiers before signing: the network name, the chain ID, and the rsETH contract displayed by Kelp. Ethereum mainnet uses chain ID 1. Arbitrum One uses 42161, Base uses 8453, and Linea uses 59144. Arbitrum One, Base, and Linea remain outside the published retirement set. The transaction interface still determines which action each route exposes. Old tutorials naming Optimism, chain ID 10, Scroll, chain ID 534352, or zkSync Era, chain ID 324, describe deployments whose Kelp bridge support has ended.

Gas, approvals, and recovery charges follow different cost drivers

Each availability path produces a different bill because minting, token approval, and recovery invoke different transactions.

Native ETH minting uses one deposit transaction after wallet connection. An ERC-20 liquid staking token such as ETHx from Stader or stETH from Lido first requires an allowance when the deposit contract lacks one, followed by a deposit transaction. The standard fresh-allowance path therefore produces two onchain confirmations. Ethereum charges gas in ETH, and 1 ETH equals 10^18 wei. An L2 charges its execution gas and may add an L1 data component. The wallet quote reflects gas demand, calldata, and contract calls rather than a fixed Kelp tariff.

Sunset recovery has fixed parts. The EVM flow requires two recorded transactions: one burn on the retired source network and one USDC payment on Ethereum. The recovery charge is 100 USDC per address, separate from the rsETH amount returned. USDC on Ethereum uses 6 decimals, so 100 tokens equal 100,000,000 base units. Source-network gas and Ethereum gas remain market-set. Small balances therefore carry a higher recovery cost relative to their size, while the fixed component remains 100 USDC per address.

Three access states lead to different workflows

Kelp access now falls into three operational states, and each state determines the next valid action.

Kelpdao availability therefore describes a state, not a permanent badge. A supported L2 route uses an automated contract workflow, whereas a sunset claim uses manual settlement. Holding rsETH on Optimism, Scroll, or another retired network does not reactivate bridging. Conversely, an rsETH balance on Arbitrum One or Base does not prove every DeFi venue accepts deposits. Chain support, token identity, route support, and application integration must align for an operation such as an Arbitrum One transaction on chain ID 42161.

Direct minting and balance usability require separate tests

Kelp treats minting availability and balance usability as separate tests because one concerns issuance, while the other concerns integrations.

On Ethereum, Kelp accepts a configured asset through its restake flow and mints rsETH at the protocol exchange rate. The rate does not promise 1 rsETH for 1 ETH; it reflects the value the protocol accounts for. A supported L2 may expose native minting, cross-chain transport, or only a venue for using an existing balance. LayerZero messaging has supplied cross-chain token transport for rsETH, while Chainlink Proof of Reserve supports reserve checks around minting. The dApp must display the exact action before the wallet requests a signature.

Asset support narrows the route further. Kelp flows have used native ETH, Stader's ETHx, and Lido's stETH as inputs, while the selector reveals what the chosen route accepts. Kelp does not treat WETH as native ETH automatically. Likewise, wrsETH uses a wrapper contract and requires the unwrap operation assigned to its network, such as native ETH minting on Ethereum mainnet.

Verification uses chain IDs, contract identities, and balance changes

Transaction verification proves Kelp availability by matching the intended chain, token contract, recipient, and resulting balance. Start with the wallet's chain ID and the contract displayed by Kelp.

An Ethereum address contains 20 bytes, displayed as 40 hexadecimal characters after the 0x prefix. A transaction hash contains 32 bytes, or 64 hexadecimal characters after 0x. These lengths distinguish an address from a hash when recording evidence. The Ethereum rsETH ERC-20 contract reports 18 decimals, so one whole token equals 10^18 base units. A successful approval changes only the allowance; the deposit needs its own successful transaction. On an L2, confirm the receipt belongs to chain ID 42161, 8453, or the other route actually selected.

Retired routes now settle through Ethereum recovery

Retired rsETH routes use a time-limited Ethereum settlement process instead of the former automated bridge workflow.

Kelp retired bridging after June 15, 2026, on 21 named networks. Movement follows a separate non-EVM verification sequence, while the other listed routes use the EVM burn flow. An eligible EVM holder unwraps wrsETH when required, sends rsETH to the published burn address, pays the Ethereum USDC charge, and retains both transaction hashes. Kelp sends the payout to the same EVM address on Ethereum mainnet. Positions inside Aave, a liquidity pool, or another contract must first return to the controlling wallet.

The recovery window lasts 12 months and closes on June 15, 2027; Kelp settles verified claims once per quarter. A full year contains four quarterly settlement periods, although submission timing determines the next batch. Movement adds a one-time exact-amount MOVE challenge with a 30-day expiry. Its process sends rsETH to the declared Ethereum address instead of using EVM same-address continuity. Retain the burn hash, fee hash, source address, destination address, and token amount until settlement completes before June 15, 2027.

Integration availability is narrower than token availability

Network support only places rsETH on a chain; each DeFi protocol makes a separate integration decision. Kelp groups Ethereum, Arbitrum One, and Base separately on its DeFi surface.

Aave availability concerns collateral listing, supply caps, borrowing settings, and market status. Pendle availability depends on a live Standardized Yield market and its maturity. Balancer or Curve liquidity requires a deployed pool with usable reserves, while Uniswap access requires a pool for the exact rsETH contract on that chain. These signals are not interchangeable. A token remains transferable when a market stops new supply, and a shallow pool supports less size than a deep one. Treat lending, liquidity, and wallet balances as different states; EigenLayer exposure does not guarantee identical downstream uses, such as Aave collateral on Base.

Ongoing maintenance starts with route status and position records

Reliable rsETH access requires a small record set and a fresh route check before every later transaction.

Keep five fields together: network name and chain ID; exact rsETH or wrsETH contract; human-readable and base-unit amounts; approval and execution transaction hashes; and the destination address, with the recovery fee hash when relevant. This record separates a display problem from a transaction problem. A wallet may hide a token while retaining its balance, and an approval persists until it is spent, reduced, or changed onchain. Recording both transactions prevents a later review from mistaking an allowance for a completed deposit.

Recheck the route whenever Kelp changes its network selector because a saved contract address does not restore a closed function. MetaMask, Rabby, Ledger, and Coinbase Wallet use the same EVM address format, although their backup procedures differ. Store the position record with the wallet's recovery materials rather than a public transaction note. Every maintenance entry should finish with a named route and identifier, such as Base chain ID 8453.