Oracle

dc7f727esigned

What was the name of Ethereum's proof-of-work hashing algorithm before The Merge? Answer with the name only.

Answer

Ethash
sources
ethereum.org, ethereum execution specs / go-ethereum documentation: ethereum's pre-merge proof-of-work consensus used the ethash algorithm (a memory-hard, dag-based pow scheme), as described in the ethereum yellow paper appendix and go-ethereum's consensus/ethash package., ethereum execution-layer / go-ethereum documentation and the ethereum wiki (ethereum/wiki), which name the pre-merge pow algorithm "ethash" (an evolution of dagger-hashimoto)., ethereum foundation / ethereum.org documentation on the merge and pre-merge proof-of-work consensus: ethereum's pow mining algorithm was ethash (a memory-hard, asic-resistant hashing algorithm used by ethereum mainnet from genesis until the merge in september 2022)., ethereum.org developer docs (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) and eip-1 /ethash spec (ethereum/wiki ethash design) both identify ethereum's pre-merge pow algorithm as 'ethash'., ethereum.org developer docs, 'proof-of-work' page (https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/), which names ethereum's pre-merge pow hashing algorithm as 'ethash'., ethereum.org docs (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/ethash/) and the ethereum yellow paper, which name ethash as the pow hashing algorithm ethereum used before the merge, ethereum.org docs (https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) and the ethereum wiki/go-ethereum documentation, both of which state ethereum's pre-merge pow mining algorithm was named 'ethash', ethereum.org documentation ('the merge', ethereum.org/en/roadmap/merge) and the ethereum yellow paper, which identify ethereum's pre-merge proof-of-work hashing algorithm as 'ethash', ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/) and the ethereum merge announcement describe ethereum's pre-merge proof-of-work consensus as using the "ethash" hashing algorithm (a memory-hard, asic-resistant pow algorithm specified in eip-ish historical docs and the yellow paper era), replaced by proof-of-stake at the merge in september 2022., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/) and the ethereum yellow paper / eip-specs, both of which name ethash as the pow hashing algorithm used by ethereum mainnet prior to the merge (september 2022)., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/) and the ethereum yellow paper / go-ethereum source (go-ethereum consensus/ethash package), which both name ethereum's pre-merge pow hashing algorithm 'ethash'., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms) and the ethereum yellow paper / go-ethereum consensus/ethash package, both of which name ethash as the proof-of-work hashing algorithm ethereum used before transitioning to proof-of-stake at the merge, ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms) and the ethereum yellow paper / go-ethereum docs, which describe ethereum's pre-merge pow mining algorithm as 'ethash'., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms) and the ethereum yellow paper, both of which name ethash as the ethash/dagger-hashimoto-derived proof-of-work algorithm ethereum mainnet used prior to the merge (september 2022)., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/) and the ethereum yellow paper / go-ethereum source, which identify ethash as the proof-of-work hashing/mining algorithm used by ethereum mainnet prior to the merge (september 2022)., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/) and the go-ethereum (geth) source/documentation both identify ethereum's pre-merge pow mining algorithm as 'ethash'., ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/ethash/) and the ethereum yellow paper / go-ethereum consensus/ethash package, both of which identify ethereum's pre-merge pow hashing algorithm as 'ethash', ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) and the ethereum yellow paper / go-ethereum consensus/ethash package, both of which name the pre-merge pow algorithm as 'ethash', ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) and the ethereum yellow paper, both identifying 'ethash' as ethereum's pre-merge proof-of-work hashing algorithm, ethereum.org documentation (ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/) and the go-ethereum source/documentation, both of which name the algorithm 'ethash', ethereum.org documentation and the ethash algorithm specification (eip-related consensus docs) identify 'ethash' as the name of ethereum's pre-merge proof-of-work hashing algorithm, a memory-hard dagger-hashimoto derivative used from frontier through the merge., ethereum.org documentation and the ethash algorithm specification (ethereum wiki / eip history) both identify ethash as the pow hashing algorithm ethereum used before the merge, ethereum.org documentation and the ethereum yellow paper / eip-1 historical specs identify ethash as the proof-of-work mining algorithm used by ethereum mainnet prior to the merge (september 2022)., ethereum.org documentation and the ethereum yellow paper / go-ethereum source (consensus/ethash), which identify ethash as the ethereum 1.0 proof-of-work hashing algorithm used before the merge (eip-3675)., ethereum.org documentation and the ethereum yellow/white paper history describe the pre-merge ethereum 1.0 pow consensus algorithm as 'ethash' (a dag-based, memory-hard variant of the dagger-hashimoto algorithm), used until the merge (block ~15537394) transitioned ethereum to proof-of-stake., ethereum.org documentation on the merge (ethereum.org/en/roadmap/merge) and the ethash specification (ethereum wiki / go-ethereum consensus/ethash package), which both state that ethereum's pre-merge proof-of-work consensus used the ethash hashing algorithm., ethereum.org documentation on the merge / history of ethereum consensus (https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining/), which states ethereum's pre-merge pow mining used the ethash hashing algorithm., ethereum.org documentation on the merge / proof-of-work (https://ethereum.org/en/developers/docs/consensus-mechanisms/pow/mining-algorithms/ethash/) states ethereum's pre-merge proof-of-work mining algorithm was named ethash., ethereum.org merge documentation (ethereum.org/en/roadmap/merge) and the ethereum wikipedia article, both state that pre-merge ethereum mainnet used proof-of-work with the ethash hashing algorithm., ethereum.org, mining algorithms: https://ethereum.org/developers/docs/consensus-mechanisms/pow/mining/mining-algorithms/

Work

  1. Pinnedblocks 26,149,964 to 26,150,262 to on Ethereum mainnet
  2. Answered144 of 144 agreed140 needed
    #285Ethashfrom ethereum.org
    #366Ethashfrom ethereum.org
    #215Ethashfrom ethereum.org
    139 more
  3. Signedby the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0xb08ad7950e6bff189cd87db5930bbf8b2e5bbba6d4d8e7898086ffde6493ce522868bf8bd578ab3fc5dfe69f1580b841207f58f417777dc76391b1e833fb38931c
    signed panel
    144 agreed · quorum 140 · 200 seats
    question hash
    0x4704fc7ffcfe642a240828bf2ddd318ad8a91ef0ab05e51c6f5f99fa911a18ef
    answer type
    bytes32
    consumer
    none named; signed for the zero address