Swell uses Chainlink Proof of Reserve to monitor ETH backing its liquid tokens

Swell uses Chainlink Proof of Reserve to report ETH backing swETH and rswETH on Ethereum. The feeds connect reserve balances with each token's underlying staking pool. Reading them requires matching the token, monitored addresses, and reporting time; reserve coverage answers a different question from withdrawal readiness or market price.

Updated 2026.10.16

The selected token determines the relevant ETH reserves

Selecting swETH or rswETH changes which staking pool the reserve report needs to cover. swETH represents liquid-staked ETH. rswETH represents ETH natively restaked through EigenLayer, with validators directed toward that protocol's contracts. Their reserve feeds refer to separate backing pools. A balance reported for swETH cannot establish how much ETH backs rswETH, even though both tokens belong to the same protocol and use Ethereum. Combining the totals would lose the connection between each token and its own backing.

How does the validator list become an onchain reserve report?

The integration calculates reserve balances for addresses that Swell reports through a wallet address manager. The address list and the balance calculation perform different jobs.

Swell's address list

The address list establishes what the feed measures. In the swETH integration, the project self-attests to ownership of the addresses listed through the IPoRAddressList interface. The reported total therefore inherits that scope. An omitted address would sit outside that particular calculation, while an incorrect address would change what the balance represents. Aggregating the balances does not independently establish ownership of every listed address.

Consensus-layer balances

The rswETH feed reports total ETH staked on Ethereum's consensus layer for the validator addresses that Swell supplies. Chainlink makes that report available onchain. The list identifies monitored validators; the report supplies their aggregate balance. Neither component, considered alone, establishes that the list captures every asset and obligation relevant to the token's complete accounting.

Token supply and ETH-denominated backing

rswETH's exchange rate connects the token supply to the underlying ETH that the tokens represent. Its repricing design reflects accrued rewards through the ETH value of each token, so the number of tokens and the number of ETH need not match.

A consistent comparison expresses both sides in ETH. For a stated supply, multiplying the token amount by the applicable ETH-per-token exchange rate gives the ETH amount that the supply represents. That conversion defines the comparison; it does not independently validate the rate.

A consensus-layer reserve report has its own measurement boundary. It reports the specified validators' staked ETH, rather than automatically describing every balance elsewhere in the protocol. Whether that report alone covers the comparison depends on the scope of the token accounting.

Matching reporting times also matters. A token-supply reading taken after a deposit can refer to a different state from an earlier reserve report. Mixing those observations can create an apparent discrepancy without establishing what changed in between.

Accounting values also differ from immediately available ETH. A balance recorded at validators remains subject to the withdrawal path, even when the reserve and token-accounting values agree.

Does reported backing make ETH immediately withdrawable?

Reported ETH backing does not make every withdrawal immediately claimable, because some underlying ETH remains staked.

Validator and restaking delays

Protocol redemptions can depend on validator exits, sweep states, and any applicable restaking withdrawal delay. Swell also documents a buffer of staking rewards and daily deposits that can fund withdrawals without exiting validators. Large requests can exceed that buffer. The reserve balance therefore cannot provide an individual completion time. For rswETH, the withdrawal interface distinguishes Pending from Claimable.

View image file

Secondary-market execution

A secondary-market sale exchanges the token at a market quote, rather than redeeming its underlying ETH through the protocol. Liquidity and trade size affect execution and slippage. Even a fully backed token can have a sale quote that differs from its primary-market exchange rate.

Proof of Reserve, price Feeds, and CCIP

Chainlink's services cover different parts of the protocol. Proof of Reserve reports collateral balances. Price Feeds supply price data, including data used to estimate transaction gas costs in dollars. The Cross-Chain Interoperability Protocol (CCIP) supports messaging for cross-chain swETH transfers. A reserve total cannot identify a market bid, and a cross-chain message does not establish the ETH backing a token.

View image file

Can reserve reporting automatically block an unsupported mint?

Automatic minting restrictions require contract logic that checks reserve data and enforces the resulting rule. A feed supplies information that such logic can use. Publishing a reserve total does not, by itself, add that safeguard to a token contract.

Swell's April 9, 2024 rswETH integration announcement described additional reserve-based ratio checks as a planned implementation. That future implementation was separate from the reserve reporting announced as integrated. The announcement does not establish the present status of those additional controls.

The active contract implementation determines which actions use the feed and what happens when a reading fails its requirements. A feed's presence alone does not specify the condition that blocks minting, the operations it covers, or the response to missing data.

View image file

Reserve data inside a DeFi position

Reserve data remains relevant when swETH or rswETH backs a position in another DeFi contract. swETH and rswETH can enter supported applications, including vault strategies. The reserve feed still concerns the staking assets behind the token; it does not certify the vault's code or determine the price at which that position can exit.

Fee Flow sits elsewhere in this accounting. Its auctions sell protocol revenue denominated in swETH and rswETH for SWELL, then burn the SWELL received. Those burns concern the governance token's supply. They do not report the ETH held by the validator pools, so an auction result cannot substitute for a reserve balance.

Report timing, penalties, and code risk

A reserve reading describes a reported state at its update time, while validator balances can change afterward. Rewards can increase underlying ETH, and validator penalties or slashing can reduce it. The feed's data-source definition and last update determine what observation a displayed total represents.

Smart-contract audits address a different risk. The July 31, 2024 rswETH v2 withdrawal release named Sigma Prime and Nethermind as auditors of that release's withdrawal code. Such review concerns that implementation's security; it does not replace measurement of later reserve balances. Equally, reporting a balance does not establish that every contract holding or using the token is free of defects.

Ethereum monitoring and the Swellchain sunset

Ethereum-based swETH and rswETH were outside the scope of the Swellchain wind-down announced on April 28, 2026. Swell's announcement left those products operating on Ethereum while shifting focus toward Faro. The L2 withdrawal timetable concerned funds on Swellchain, rather than imposing a redemption deadline on Ethereum token holders. If the monitored addresses or underlying balances change, an earlier report no longer describes the same reserve state.