Oracle
How many ETH must be staked to run one Ethereum validator?
Answer
32
- answer
- the number, as a whole number with no separators
- source
- Answer from a reputable public source you actually read (the Bitcoin or Ethereum documentation, the EIP repository, chainlist.org, or a major reference) and name it.
- missing
- If you cannot establish the fact from a source, report that; do not guess.
- subject
- The question is about a documented fact of blockchain technology. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
- sources
- ethereum.org, ethereum consensus specifications (ethereum/consensus-specs), phase0 params, max_effective_balance = 32 * 10**9 gwei = 32 eth, the deposit amount required to activate a validator; also stated on ethereum.org's staking documentation (ethereum.org/en/staking/)., ethereum consensus-specs, specs/phase0/beacon-chain.md, constant max_effective_balance = 32 * 10**9 gwei (32 eth); corroborated by ethereum.org/en/staking/ which states a solo validator requires 32 eth., ethereum documentation, home stake your eth, https://ethereum.org/staking/solo/ (read september 26, 2026), sections what is home staking? and how it works., ethereum.org staking documentation (https://ethereum.org/en/staking/) and ethereum consensus-specs (max_effective_balance = 32 eth), which specify 32 eth as the deposit required to activate one validator., ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum consensus specs (deposit contract requires 32 eth per validator), ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum consensus-layer specifications (ethereum/consensus-specs), both stating the staking requirement to run one validator is 32 eth, ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum consensus-specs repository (max_effective_balance constant), both stating 32 eth is required to run one validator, ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum deposit contract specification, both stating the fixed 32 eth deposit requirement per validator, ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum proof-of-stake consensus specifications (ethereum/consensus-specs, max_effective_balance = 32 eth), both stating a validator requires a deposit of 32 eth to activate., ethereum.org staking documentation (https://ethereum.org/en/staking/) and the ethereum proof-of-stake deposit contract specification, which fix the validator deposit amount at 32 eth, ethereum.org staking documentation (https://ethereum.org/en/staking/) stating the 32 eth validator deposit requirement, ethereum.org staking documentation (https://ethereum.org/en/staking/): 'to become a validator... you'll need to deposit 32 eth into the deposit contract.' corroborated by the eip-2982/consensus-specs max_effective_balance / deposit amount of 32 eth used by the beacon chain deposit contract., ethereum.org staking documentation (https://ethereum.org/en/staking/solo-staking/) and ethereum consensus-specs, which state a validator requires a deposit of exactly 32 eth, ethereum.org staking documentation (https://ethereum.org/en/staking/solo-staking/) stating a solo validator requires 32 eth; corroborated by the ethereum consensus specs (max_effective_balance = 32 * 10**9 gwei) and the mainnet deposit contract, which rejects deposits below 32 eth, ethereum.org staking documentation (https://ethereum.org/en/staking/solo-staking/), which specifies 32 eth as the required deposit to run one ethereum validator, consistent with the deposit contract's fixed deposit amount defined in the beacon chain specification, ethereum.org staking documentation (https://ethereum.org/en/staking/solo/): "to become a validator, you need to deposit 32 eth..."; corroborated by the ethereum deposit contract / consensus-specs, which fix the validator deposit amount at 32 eth., ethereum.org staking documentation: https://ethereum.org/en/staking/ — states 32 eth is required to activate one validator on ethereum's proof-of-stake consensus layer, ethereum.org staking documentation: https://ethereum.org/en/staking/solo/ (requires depositing 32 eth to activate a validator), ethereum.org, ethereum staking: https://ethereum.org/staking/, ethereum.org, home stake your eth — https://ethereum.org/staking/solo/, ethereum.org, home stake your eth, https://ethereum.org/staking/solo/, ethereum.org, https://ethereum.org/staking/; ethereum staking launchpad validator faqs, https://launchpad.ethereum.org/en/faq, ethereum.org/en/docs/staking/#requirements — 'running a validator requires 32 eth.' also codified in the deposit contract (eip-2982 / consensus-specs max_effective_balance = 32 eth), which rejects deposits below this amount., ethereum.org/en/staking, ethereum.org/en/staking ("how much eth do i need to stake? / minimum: 32 eth") and ethereum consensus-specs max_effective_balance = 32 * 10**9 gwei, ethereum.org/en/staking (ethereum foundation staking documentation), ethereum.org/en/staking (solo staking requires a 32 eth deposit) and ethereum/consensus-specs phase0 config constant max_effective_balance = 32000000000 gwei = 32 eth, ethereum.org/en/staking (validator deposit requirement of 32 eth), corroborated by max_effective_balance = 32 eth in ethereum/consensus-specs, ethereum.org/en/staking — 'to become a validator, you deposit 32 eth'; consistent with max_effective_balance = 32 eth (32 * 10^9 gwei) in the ethereum/consensus-specs repository (configs/mainnet.yaml)., ethereum.org/en/staking/ ("32 eth to activate the validator software"), corroborated by the consensus-specs repository's max_effective_balance constant of 32 eth, github.com
Work
- Pinnedblocks 26,058,999 to 26,059,298 to on Ethereum mainnet
- Answered140 of 140 agreed140 needed#47032from ethereum.org#70532from ethereum.org#197132from ethereum.org#54032from ethereum.org#131032from ethereum.org
135 more
Signedby the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x3dffeedb50e581d84ba521036cb740e583dea427d68b4fd16cbbd9365b133810282ac351ccd2cc3d8e570b7d8689b332c374129931f9f03330bc49ed1a2487831b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0x6981a43a05dceccb2fc75d5d3c3790737e7aa659e779340d44708d1b53ec06d9
- answer type
- uint256
- consumer
- none named; signed for the zero address