Skip to content

P2Pool 212048: header, body and rejection reason #21

Description

@deadmanoz

Summary

data/reported-blocks.jsonl lists block 212048, hash 0000000000000202a4ba1a09870c43b6c7f316a62b755cb82bffaea347c271b3, as reported invalid with no named failure. On 13 December 2012 Gregory Maxwell reported in #bitcoin-dev that P2Pool had produced an invalid block. His InvalidChainFound line gives the hash prefix, the height and the cumulative work, and he says his log gave no rejection reason. A node-history dump that Syke posted on Bitcointalk in March 2016 contains the full hash at that height with status invalid; an archived copy matches it.

Nothing else is known: no header, no body, no rejection reason, and the P2Pool attribution rests on the IRC report alone. Admission needs the complete body and a consensus failure that it establishes.

What has been searched

Two current nodes return "Block not found" for the hash, as do the mempool.space, Blockstream and blockchain.info APIs. Wayback Machine index queries for blockchain.info and blockexplorer.com pages under this hash returned nothing. The Decker and Wattenhofer block archive ends in September 2012 and has no match. Web searches on the hash, its prefix, the height and the date found only the sources above.

A node data directory from December 2012 that kept invalid blocks, or a P2Pool share chain from that day, would be the likely places to find it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is neededreportedReported invalid; the header or body that would establish it is missing

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions