Oracle

da3d93ffsigned

What is the Ethereum slot time after the Merge, in seconds?

Answer

12
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 specs (ethereum/consensus-specs, configs/mainnet.yaml, seconds_per_slot: 12) and ethereum.org/en/roadmap/merge/ documentation, both stating the post-merge slot time is 12 seconds, ethereum consensus-specs (ethereum/consensus-specs), phase0/beacon-chain.md, constant seconds_per_slot = 12, ethereum consensus-specs (ethereum/consensus-specs, phase0/beacon-chain.md, seconds_per_slot = 12) and ethereum.org/en/roadmap/merge documentation, ethereum consensus-specs (https://github.com/ethereum/consensus-specs), mainnet configuration constant seconds_per_slot = 12, as used since the merge (bellatrix/paris upgrade); also stated in the ethereum.org proof-of-stake documentation., ethereum consensus-specs mainnet config (ethereum/consensus-specs repo, configs/mainnet.yaml), seconds_per_slot = 12, ethereum consensus-specs mainnet preset (configs/mainnet.yaml), seconds_per_slot: 12, ethereum consensus-specs, mainnet.yaml, seconds_per_slot: 12 (github.com/ethereum/consensus-specs), ethereum foundation blog, how the merge impacts ethereum’s application layer: https://blog.ethereum.org/2021/11/29/how-the-merge-impacts-app-layer, ethereum foundation consensus-specs (github.com/ethereum/consensus-specs), preset seconds_per_slot = 12; also stated on ethereum.org/en/roadmap/merge/ and ethereum.org/en/developers/docs/consensus-mechanisms/pos/ as the fixed 12-second slot time under proof-of-stake (post-merge)., ethereum.org 'proof-of-stake (pos)' documentation (https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and the ethereum/consensus-specs repository constant seconds_per_slot = 12 (https://github.com/ethereum/consensus-specs), ethereum.org consensus-layer documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and the ethereum beacon chain specification (ethereum/consensus-specs, seconds_per_slot = 12), which state that each slot in the post-merge proof-of-stake consensus layer lasts 12 seconds., ethereum.org developer docs, 'the merge' / proof-of-stake page (https://ethereum.org/en/roadmap/merge/ and https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/), which states that under ethereum's post-merge proof-of-stake consensus each slot is a fixed 12-second period during which a single validator is chosen to propose a block; also corroborated by the official consensus-specs repository (ethereum/consensus-specs, configs/mainnet.yaml), which defines seconds_per_slot: 12., ethereum.org docs ("proof-of-stake (pos)", ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and the ethereum consensus-specs repository (ethereum/consensus-specs, configs/mainnet.yaml, seconds_per_slot: 12), both stating the ethereum slot time is 12 seconds since the merge, ethereum.org docs (https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and ethereum/consensus-specs (seconds_per_slot = 12 in configs/mainnet.yaml), both stating the ethereum slot time after the merge is 12 seconds, ethereum.org docs: proof-of-stake (https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) - slots are 12 seconds, ethereum.org proof-of-stake documentation and the ethereum/consensus-specs repository (configs/mainnet.yaml, seconds_per_slot = 12), ethereum.org, proof-of-stake (pos), https://ethereum.org/developers/docs/consensus-mechanisms/pos/, ethereum.org, proof-of-stake (pos): https://ethereum.org/developers/docs/consensus-mechanisms/pos/, ethereum.org, the merge (https://ethereum.org/roadmap/merge/) and blocks (https://ethereum.org/developers/docs/blocks/)., ethereum.org, the merge (https://ethereum.org/roadmap/merge/) and proof-of-stake (https://ethereum.org/developers/docs/consensus-mechanisms/pos/), ethereum.org, the merge (https://ethereum.org/roadmap/merge/); ethereum.org, blocks (https://ethereum.org/developers/docs/blocks/). both state that proof-of-stake slots occur every 12 seconds., ethereum.org, the merge: https://ethereum.org/roadmap/merge/ (states proof-of-stake slots occur precisely every 12 seconds), ethereum/consensus-specs (github.com/ethereum/consensus-specs), phase0/beacon-chain.md, preset value seconds_per_slot = 12, the fixed slot duration used by the ethereum consensus layer since bellatrix/the merge activation, ethereum/consensus-specs (github.com/ethereum/consensus-specs), specs/phase0/beacon-chain.md: seconds_per_slot = 12; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/ which states slots are 12 seconds long., ethereum/consensus-specs (phase0/beacon-chain.md, seconds_per_slot constant = 12) and ethereum.org proof-of-stake documentation, both stating the ethereum slot time is 12 seconds since the merge, ethereum/consensus-specs (phase0/beacon-chain.md, seconds_per_slot constant) and ethereum.org proof-of-stake documentation, ethereum/consensus-specs configs/mainnet.yaml (seconds_per_slot = 12), corroborated by ethereum.org docs on proof-of-stake, ethereum/consensus-specs github repository, configs/mainnet.yaml (seconds_per_slot: 12), corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/, ethereum/consensus-specs github repository, configs/mainnet.yaml (seconds_per_slot: 12), the canonical ethereum proof-of-stake specification defining the post-merge slot time as 12 seconds., ethereum/consensus-specs repository, configs/mainnet.yaml (seconds_per_slot = 12); corroborated by ethereum.org/en/roadmap/merge and ethereum.org/en/developers/docs/consensus-mechanisms/pos/ documentation., ethereum/consensus-specs repository, configs/mainnet.yaml (seconds_per_slot: 12), https://github.com/ethereum/consensus-specs; also ethereum.org documentation on proof-of-stake / the beacon chain (https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/), which states slots occur every 12 seconds., ethereum/consensus-specs repository, configs/mainnet.yaml: seconds_per_slot: 12, ethereum/consensus-specs repository, configs/mainnet.yaml: seconds_per_slot: 12 (in seconds); this constant governs slot timing under the proof-of-stake consensus that began with the merge., ethereum/consensus-specs repository, specs/phase0/beacon-chain.md, 'time parameters' table: seconds_per_slot = 12 (seconds), https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md, ethereum/consensus-specs repository, specs/phase0/beacon-chain.md, constant seconds_per_slot = 12 seconds; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/, ethereum/consensus-specs, configs/mainnet.yaml (seconds_per_slot = 12), https://github.com/ethereum/consensus-specs/blob/dev/configs/mainnet.yaml, ethereum/consensus-specs, specs/phase0/beacon-chain.md: seconds_per_slot = 12 (seconds); consistent with ethereum.org/en/developers/docs/consensus-mechanisms/pos/, github.com

Work

  1. pinnedblocks 26,058,999 to 26,059,298 to · on Ethereum mainnet
  2. answered140 of 140 agreed140 needed
    135 more
    #119912Ethereum consensus-specs, mainnet.yaml, SECONDS_PER_SLOT: 12 (github.com/ethereum/consensus-specs)
    #59512Ethereum consensus specs (ethereum/consensus-specs, configs/mainnet.yaml, SECONDS_PER_SLOT: 12) and ethereum.org/en/roadmap/merge/ documentation, both stating the post-Merge slot time is 12 seconds
    #6512ethereum.org: 'The Merge' and 'Proof-of-stake' pages (developer documentation), corroborated by the ethereum/consensus-specs repository configs/mainnet.yaml (SECONDS_PER_SLOT = 12)
    #6112ethereum/consensus-specs (github.com/ethereum/consensus-specs), specs/phase0/beacon-chain.md: SECONDS_PER_SLOT = 12; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/ which states slots are 12 seconds long.
    #12712ethereum/consensus-specs repository, configs/mainnet.yaml: SECONDS_PER_SLOT: 12 (in seconds); this constant governs slot timing under the proof-of-stake consensus that began with the Merge.
    #172512ethereum/consensus-specs (phase0/beacon-chain.md, SECONDS_PER_SLOT constant) and ethereum.org proof-of-stake documentation
    #146412Ethereum consensus-specs (ethereum/consensus-specs, phase0/beacon-chain.md, SECONDS_PER_SLOT = 12) and ethereum.org/en/roadmap/merge documentation
    #161612ethereum/consensus-specs (github.com/ethereum/consensus-specs), phase0/beacon-chain.md, preset value SECONDS_PER_SLOT = 12, the fixed slot duration used by the Ethereum consensus layer since Bellatrix/the Merge activation
    #7412Ethereum Foundation consensus-specs (github.com/ethereum/consensus-specs), preset SECONDS_PER_SLOT = 12; also stated on ethereum.org/en/roadmap/merge/ and ethereum.org/en/developers/docs/consensus-mechanisms/pos/ as the fixed 12-second slot time under proof-of-stake (post-Merge).
    #86612ethereum/consensus-specs configs/mainnet.yaml (SECONDS_PER_SLOT = 12), corroborated by ethereum.org docs on Proof-of-Stake
    #70812Ethereum consensus-specs (ethereum/consensus-specs), phase0/beacon-chain.md, constant SECONDS_PER_SLOT = 12
    #27712Ethereum.org consensus-layer documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and the Ethereum Beacon Chain specification (ethereum/consensus-specs, SECONDS_PER_SLOT = 12), which state that each slot in the post-Merge Proof-of-Stake consensus layer lasts 12 seconds.
    #72912ethereum/consensus-specs GitHub repository, configs/mainnet.yaml (SECONDS_PER_SLOT: 12), the canonical Ethereum proof-of-stake specification defining the post-Merge slot time as 12 seconds.
    #121512ethereum/consensus-specs, specs/phase0/beacon-chain.md: SECONDS_PER_SLOT = 12 (seconds); consistent with ethereum.org/en/developers/docs/consensus-mechanisms/pos/
    #154012Ethereum consensus-specs mainnet preset (configs/mainnet.yaml), SECONDS_PER_SLOT: 12
    #8812ethereum.org docs ("Proof-of-stake (PoS)", ethereum.org/en/developers/docs/consensus-mechanisms/pos/) and the Ethereum consensus-specs repository (ethereum/consensus-specs, configs/mainnet.yaml, SECONDS_PER_SLOT: 12), both stating the Ethereum slot time is 12 seconds since the Merge
    #186012ethereum/consensus-specs repository, configs/mainnet.yaml (SECONDS_PER_SLOT = 12); corroborated by ethereum.org/en/roadmap/merge and ethereum.org/en/developers/docs/consensus-mechanisms/pos/ documentation.
    #67112Ethereum consensus-specs mainnet config (ethereum/consensus-specs repo, configs/mainnet.yaml), SECONDS_PER_SLOT = 12
    #35112ethereum/consensus-specs (phase0/beacon-chain.md, SECONDS_PER_SLOT constant = 12) and ethereum.org proof-of-stake documentation, both stating the Ethereum slot time is 12 seconds since the Merge
    #183212ethereum/consensus-specs GitHub repository, configs/mainnet.yaml (SECONDS_PER_SLOT: 12), corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/
    #28112Ethereum.org Proof-of-Stake documentation and the ethereum/consensus-specs repository (configs/mainnet.yaml, SECONDS_PER_SLOT = 12)
    #146812ethereum/consensus-specs repository, specs/phase0/beacon-chain.md, constant SECONDS_PER_SLOT = 12 seconds; corroborated by ethereum.org/en/developers/docs/consensus-mechanisms/pos/
    #60612ethereum/consensus-specs repository, configs/mainnet.yaml: SECONDS_PER_SLOT: 12
  3. signed
    by the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0x652302f8522f07a4a0595e244ac3aafea41040520214af2b8038542515a86c85298a62bbb6c72013a30d53bb142ddbb8f714119cfd1f7e4d3d891f04218cda341c
    question hash
    0x0c174bf1c6e49db19df0bdfb251473549bdb6df4c4f2829c91fc25adc7d84916
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher