Liquid staked Ether 2.0 (stETH) — what its owner can do

Ethereum · 0xae7ab96520de3a18e5e111b5eaab095312d7fe84
Read from the chain on 2026-10-14. All checks completed.

This address is a proxy. The checks below were run against the implementation it delegates to, 0x028271e30a695c0527a0c50ca30603fed004cdb0, since that is the code that actually runs.

Who can do these things

No privileged address could be identified. This is not the same as there being none — see the limitation below.

Only named getters were read. If this contract uses role-based access control without enumeration, its role holders cannot be listed, and the absence of a controller here does not mean there is none.

What the contract permits

Present

Can new tokens be created?

New tokens can be created after deployment.

Whoever holds that permission can increase the supply, which reduces the share each existing token represents.

  • mintExternalShares(address,uint256)
  • mintShares(address,uint256)

Whether minting has been used, and under what constraints, is not established here.

Not present

Can transfers be blocked?

No mechanism was found that would let anyone block a transfer.

  • No address blocking, pause, trading switch or transfer cap in the ABI
Not present

Is there a trading tax?

No trading tax mechanism was found.

  • No tax setter or tax rate in the ABI
Present

Can the contract logic be replaced?

The contract logic can be replaced.

Everything else described here reflects the code running today, and could be changed by whoever holds the upgrade rights.

  • The block explorer resolves this as a proxy for 0x028271e30a695c0527a0c50ca30603fed004cdb0
  • It uses a non-standard storage slot, so the upgrade rights could not be read on-chain

Who holds the upgrade rights was not determined.

Present

Is the liquidity locked?

The trading liquidity can be withdrawn by whoever holds the LP tokens.

Withdrawing liquidity leaves holders with tokens and no pool to sell them into. This is the mechanism behind most losses described as rug pulls.

  • Uniswap V2 WETH pool at 0x4028DAAC072e492d34a3Afdbef0ba7e35D8b55C4: 42.471 WETH of depth, 0% of its LP supply burned
  • Uniswap V2 USDT pool at 0x648Ef94C6D205016A385Fb4C54aB6e422F5142c5: 2.7197 USDT of depth, 0% of its LP supply burned
  • SushiSwap WETH pool at 0xe43D6AAFce76f53670C4b7D6B38A7D8a67a4B670: 0.0081 WETH of depth, 0% of its LP supply burned
  • SushiSwap USDC pool at 0x3CFAbf0A09B8EA1D655E82a7E5786dE66Eea9261: 0.0361 USDC of depth, 37.8% of its LP supply burned

Who holds the unburned LP tokens cannot be established: ERC20 holders cannot be enumerated over RPC. It may sit in a time-lock contract, or in a wallet, and this check cannot tell those apart.

This is not advice, and it is not complete. It reports what the contract allows and who can act on it. It cannot tell you whether anyone intends to. Treat a clean report as the absence of one kind of evidence, not as a recommendation.

Check another

← Back to the checker