Docs Xyz — Running an Ethereum proof-of-stake | docs.zstake.xyz

32 ETH and 27 Hours

Docs Xyz — Running an Ethereum proof-of-stake | docs.zstake.xyz

A validator goes live on a 32 ETH deposit, and everything that follows is scheduled in epochs of 8,192 twelve-second slots — 98,304 seconds, about 27.3 hours each. Getting the ETH back out means signing a voluntary exit and waiting through a queue that can be reported for up to 256 epochs, about 27 hours, before the withdrawal is paid.

Chronology

This is not a staking service, a pool prospectus or a yield advertisement — nothing here takes deposits, signs up customers or promises a return.

32 ETHin this record

Six numbers worth memorising

Scroll the strip sideways — 6 cards.

Deposit

32 ETH to activate

One validator, one deposit of 32 ETH. The deposit can sit unpublished for most of a day before activation.

Clock

27.3 hours per epoch

An epoch is 8,192 slots of 12 seconds — 98,304 seconds. Every queue and penalty is counted in these units.

Exit

Up to 256 epochs out

A signed exit is reported in the queue for up to 256 epochs, about 27 hours, before the withdrawal is paid.

Penalty

1/64 minimum forfeit

A double sign or surround vote costs at least 0.5 ETH on 32 ETH, plus a quadratic penalty, plus a 2-epoch exit.

Duty

One attestation per epoch

With 256 committees per epoch — 8,192 slots over 32 slots per committee — each validator attests exactly once per epoch.

Ceiling

2,048 ETH after Pectra

EIP-7251 raised the maximum effective balance from 32 ETH to 2,048 ETH; a 0x02 BLS credential marks the compounding layer.

Three further files

Inside this reference

2,048 ETHmaximum effective balance after PectraEIP-7251 raised the cap from 32 ETH, and a 0x02 BLS withdrawal credential marks the compounding layer.
512validators in one sync committeeA sync committee period runs 256 consecutive epochs, about 291 days, and pays roughly 2.5 times the base attestation reward for the whole period.
3.2 ETHone year on 32 ETH at a 10% yieldRewards move in whole-ETH steps because the effective balance is rounded down to an integer before anything is credited.

Set up in order: from keys to first attestation

The deposit is 32 ETH, and it only starts earning after the network publishes and activates it — a wait that can take most of a day.

The unit of account here is the epoch: 8,192 slots of 12 seconds each, 98,304 seconds, about 27.3 hours. Activation, attestation duty, the exit queue and the penalty clock are all scheduled in epochs, so every planning figure on this page converts back to hours through that one constant.

A fresh 32 ETH deposit can sit unpublished for most of a day before the validator appears in the active set. That gap is normal; it is the deposit working through the same epoch schedule that governs everything else, not a sign that the transaction failed.

While the deposit waits, the operator brings up the client pair — one execution client and one consensus client — and keeps both in sync. The validator attests once per epoch, and 8,192 slots divided by 32 slots per committee gives 256 committees per epoch for the network to spread that duty across.

  • Generate the validator keys and choose the withdrawal credential — after Pectra, a 0x02 BLS credential marks the compounding layer.
  • Send the 32 ETH deposit and expect it to sit unpublished for most of a day.
  • Bring up the execution client and the consensus client and let both fully sync.
  • Confirm activation, then watch for the first attestation — one is due each epoch.
  • Monitor the effective balance; rewards credit in whole-ETH steps because the balance rounds down.

Planning figures

The figures an operator actually plans around
What you are measuringValueUnitWhy it matters
Activation deposit32ETHthe fixed ticket that puts one validator live
One epoch98,304seconds8,192 slots of 12 seconds; about 27.3 hours
Deposit publishing waitup to about 24hoursa fresh deposit can sit unpublished for most of a day
Exit queue stayup to 256epochsreported for about 27 hours before payout
Minimum slashing forfeit0.5ETH1/64 of a 32 ETH stake, before the quadratic penalty
Exit after slashing2epochsqueued automatically once the offence is proven
Maximum effective balance2,048ETHthe EIP-7251 ceiling shipped with Pectra
Sync committee period256epochs512 validators, about 291 days, roughly 2.5 times base reward
The figures an operator actually plans around

The lifecycle, drawn to waiting time

Stages are spaced by how long they actually take, not by how they look on a roadmap.

EpochEffective balanceExit queueDouble sign
The key terms of this guide, drawn to one scale

What operators actually ask

Can I run a validator with less than 32 ETH?
No — activation happens on a 32 ETH deposit. Smaller amounts only participate through pooled arrangements, which are outside the scope of this page.
If I sign an exit today, when is the ETH spendable?
Not immediately. The validator is reported in the exit queue for up to 256 epochs, about 27 hours, and the withdrawal is paid only after that wait.
Will I get slashed if my machine goes offline for a weekend?
Downtime costs missed rewards, not slashing — missing attestations on both sides of a slot is not a slashable offence. Slashing requires a double sign or a surround vote, and if the client is offline past about 27 hours it must resynchronise from a checkpoint.
Do rewards compound on their own?
Rewards credit in whole-ETH steps because the effective balance rounds down to an integer. After Pectra, a 0x02 BLS withdrawal credential marks the compounding layer, which lets the balance grow toward the 2,048 ETH ceiling under EIP-7251.