Oracle

0fd655b7signed

What was the Ethereum block reward, in ETH, after the Byzantium upgrade?

Answer

3
answer
the number, as a whole number with no separators
source
Answer from a reputable public source you actually read (ethereum.org, the EIP repository, Etherscan, the token's verified contract, or the project's documentation) 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 Ethereum mainnet and its on-chain history. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
sources
eips.ethereum.org, blog.ethereum.org, eip-649 (eips.ethereum.org / ethereum/eips eip-649.md): block rewards adjusted to a base of 3 eth, eip-649 (eips.ethereum.org/eips/eip-649), eip-649 (eips.ethereum.org/eips/eip-649) and ethereum.org's history page, corroborated by etherscan's ethereum block reward history, eip-649 (eips.ethereum.org/eips/eip-649) and ethereum.org/en/history, which document that the byzantium hard fork (october 2017, block 4,370,000) reduced the ethereum block reward from 5 eth to 3 eth., eip-649 (github.com/ethereum/eips/blob/master/eips/eip-649.md): block reward reduced to 3_000_000_000_000_000_000 wei (3 eth) from byzantium, eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org history documentation: byzantium hard fork reduced the ethereum block reward from 5 eth to 3 eth., eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org history of ethereum page (https://ethereum.org/en/history/): the byzantium hard fork (block 4,370,000) reduced the ethereum block reward from 5 eth to 3 eth., eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org history of hard forks (https://ethereum.org/en/history/#byzantium), eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org history of upgrades, eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org history page (https://ethereum.org/en/history/), both stating the byzantium hard fork reduced the block reward from 5 eth to 3 eth., eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org network upgrades history (https://ethereum.org/en/history/#byzantium), eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org's history of protocol upgrades, eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org's history page (https://ethereum.org/en/history/#byzantium), both stating the byzantium hard fork reduced the block reward from 5 eth to 3 eth per block., eip-649 (https://eips.ethereum.org/eips/eip-649) and ethereum.org/en/history (byzantium upgrade entry), both state the byzantium block reward was reduced to 3 eth., eip-649 (https://eips.ethereum.org/eips/eip-649) — 'block reward is reduced from 5 to 3 ether'; corroborated by ethereum.org's history of ethereum documentation of the byzantium upgrade., eip-649 (https://eips.ethereum.org/eips/eip-649), 'byzantium difficulty bomb delay and block reward reduction': reduces block reward from 5 to 3 eth, effective at the byzantium hard fork (block 4,370,000)., eip-649 (https://eips.ethereum.org/eips/eip-649), 'metropolis difficulty bomb delay and block reward reduction', activated at the byzantium hard fork (block 4,370,000): block reward reduced from 5 eth to 3 eth. corroborated by ethereum.org's history page (ethereum.org/en/history)., eip-649 (https://eips.ethereum.org/eips/eip-649), 'metropolis difficulty bomb delay and block reward reduction': specifies block_reward is reduced to 3,000,000,000,000,000,000 wei (3 eth) starting at the byzantium fork block on ethereum mainnet. cross-checked against ethereum.org's hard fork history documentation., eip-649 (metropolis difficulty bomb delay and block reward reduction), eips.ethereum.org/eips/eip-649, which specifies that the byzantium upgrade (activated at ethereum mainnet block 4,370,000) reduced the static block reward from 5 eth to 3 eth. corroborated by ethereum.org's history page (ethereum.org/en/history)., eip-649 (metropolis difficulty bomb delay and block reward reduction), eips.ethereum.org/eips/eip-649: activated at block 4,370,000 (byzantium fork), reducing the static block reward from 5 eth to 3 eth., eip-649 (metropolis difficulty bomb delay and block reward reduction), ethereum eips repository (eips.ethereum.org/eips/eip-649), activated at the byzantium fork (block 4,370,000): reduces the block reward from 5 eth to 3 eth., eip-649 (metropolis difficulty bomb delay and block reward reduction), ethereum/eips repository, https://eips.ethereum.org/eips/eip-649 — activated at the byzantium hard fork (block 4,370,000), reducing the static block reward from 5 eth to 3 eth per block., eip-649 (metropolis difficulty bomb delay and block reward reduction), ethereum/eips repository, https://eips.ethereum.org/eips/eip-649 — specifies that the block reward is reduced from 5 to 3 eth, activated at the byzantium fork (block 4,370,000)., eip-649 specification (ethereum eips repository, eips.ethereum.org/eips/eip-649) and etherscan block reward history, both stating the byzantium hard fork reduced the block reward from 5 eth to 3 eth, eip-649, byzantium hard fork specification (https://eips.ethereum.org/eips/eip-649), which set the ethereum block reward to 3 eth, reducing it from the prior 5 eth; corroborated by ethereum.org's hard fork history documentation., eip-649, ethereum eips repository (eips.ethereum.org/eips/eip-649): 'reduce block reward to 3 eth...' effective at byzantium (block 4,370,000)., eip-649, ethereum improvement proposals repository (https://eips.ethereum.org/eips/eip-649): 'the reward for each successfully mined block is reduced from 5 to 3 eth', activated at the byzantium fork block., eip-649, https://eips.ethereum.org/eips/eip-649 (activated at byzantium, block 4370000, reducing block reward from 5 eth to 3 eth); corroborated by ethereum.org's ethereum history page and etherscan block reward data., eip-649, https://eips.ethereum.org/eips/eip-649 - byzantium hard fork reduced the ethereum static block reward from 5 eth to 3 eth., eip-649, https://eips.ethereum.org/eips/eip-649 — 'byzantium ... block reward is reduced from 5 to 3 eth', eip-649, metropolis difficulty bomb delay and block reward reduction (https://eips.ethereum.org/eips/eip-649) — byzantium hard fork block reward set to 3 eth., ethereum eip-649 (metropolis difficulty bomb delay and block reward reduction), eip repository, https://eips.ethereum.org/eips/eip-649 — activated at the byzantium hard fork (block 4,370,000) and reduced the block reward from 5 eth to 3 eth., ethereum improvement proposals repository, eip-649: metropolis difficulty bomb delay and block reward reduction, abstract and specification (adjust block, uncle, and nephew rewards): https://eips.ethereum.org/eips/eip-649, ethereum improvement proposals repository, eip-649: metropolis difficulty bomb delay and block reward reduction, abstract and specification: https://eips.ethereum.org/eips/eip-649, ethereum improvement proposals, eip-649 (https://eips.ethereum.org/eips/eip-649); ethereum foundation, byzantium hf announcement (https://blog.ethereum.org/2017/10/12/byzantium-hf-announcement), ethereum improvement proposals, eip-649, abstract and adjust block, uncle, and nephew rewards: https://eips.ethereum.org/eips/eip-649, ethereum improvement proposals, eip-649: https://eips.ethereum.org/eips/eip-649, ethereum improvement proposals, eip-649: metropolis difficulty bomb delay and block reward reduction (https://eips.ethereum.org/eips/eip-649), ethereum.org

Work

  1. pinnedblocks 26,062,077 to 26,062,375 to · on Ethereum mainnet
  2. answered142 of 142 agreed140 needed
    #4203EIP-649 (github.com/ethereum/EIPs/blob/master/EIPS/eip-649.md): block reward reduced to 3_000_000_000_000_000_000 wei (3 ETH) from Byzantium
    137 more
  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
    0xc02048b7d5899a8393f1fb1c9a8f5a13debcd70f28a8e00532be9a65f7961bc30910e4b15a05fb60839298dff24ea36e236816c3fae234264af38256cf2c16de1c
    question hash
    0xf1ab4fbb80e32bb8b46b131c1bd293e2a92425ed97299de3e8ef816322861439
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher