Bitcoin BIP110

Sources and policy

Evidence before claims

This reference separates the original proposal, the historical enforcement branch, the independent-chain project, and Bitcoin BTC mainnet. Each status claim should be dated and traceable to primary evidence.

Scope distinction

Four terms with different meanings

Release candidates, implementation pull requests, and live network observations are related evidence. They do not describe the same stage of development.

BIP 110

The original Reduced Data Temporary Softfork proposal.

BIP 110 enforcement branch

The historical SHA-256d chain created when enforcing nodes rejected non-signaling blocks at height 961,632.

Bitcoin BTC mainnet

The SHA-256d network that accepted the non-signaling block at height 961,632 and continued on that history.

Bitcoin BIP110

The independent native coin that continues the BIP 110 enforcement branch under BLAKE2b proof of work using Bitcoin Knots as the reference implementation.

The BLAKE2b implementation, opt-in unified signature hash, release candidates, mainnet activation block, and final 29.4.1 release are separate evidence sources. Historical testnet candidates remain useful for tracing the implementation path but do not define current mainnet state.

Source library

Primary evidence

Source code, signed tags, chain records, proposal history, and operational test records form the evidence base for this content snapshot.

01 Official BIP 110 specification Proposal text, status, changelog, and deployment rules 02 BIP 110 discussion Bitcoin development mailing-list discussion 03 BIP 110 test vectors Official repository vectors for the proposal 04 BLAKE2b proof-of-work implementation Bitcoin Knots pull request #359 05 Unified signature-hash implementation Bitcoin Knots pull request #357 06 Bitcoin BIP110 block explorer Observed Bitcoin BIP110 blocks, transactions, addresses, and timestamps 07 Bitcoin Knots RC2 source tag Signed testnet4 release-candidate source 08 BLAKE2b testnet4 mining guide Independent test record and operational warnings 09 BLAKE2b-capable DATUM Gateway Mining job construction and hardware-profile support 10 Chain-split Lightning risk analysis Operational analysis for Lightning channels 10Bitcoin Knots 29.4.1 production releaseSigned production release carrying the BLAKE2b mainnet consensus changes 11First BLAKE2b mainnet blockHeight 961,640 and the first version-2 BLAKE2b block hash

Evidence labels

A shared vocabulary for uncertainty

Verified

Confirmed by a primary source or reproducible observation.

Reported

Published by an identified source but not independently reproduced.

Proposed

Announced or coded but not active on the relevant network.

Unknown

Adequate evidence is unavailable.

Disputed

Credible sources conflict. The competing evidence should be shown together.

Obsolete

Applies to an abandoned test chain, superseded release, or historical network state.

Editorial and operational policy

What the reference records

Network-status statements use an observation date. Conflicting chain tips or maintainer claims should present both sources and the verification method. Obsolete or unsafe software links should retain historical context without being presented as current software.

  • Separate announcements from implemented and activated changes
  • Use exact dates, heights, hashes, tags, and commits
  • Identify whether evidence applies to testnet or mainnet
  • Do not infer mainnet parameters from a testnet release candidate
  • Time-stamp observed network tips and compatibility reports
  • Require service announcements before listing market support
  • Publish corrections with changed claims and their evidence
  • Preserve disputes when primary sources materially conflict

Current disclosure status: The supplied content does not include named site owners, funding sources, a public corrections address, or a security-reporting contact. Those items remain unpublished rather than inferred.

Site identity

An independent community reference

This site documents Bitcoin BIP110 and does not imply affiliation with Bitcoin Core, Bitcoin Knots, miners, exchanges, wallet vendors, or infrastructure providers unless a relationship is formally documented. It does not document Bitcoin Purity or other BIP 110-associated networks beyond brief lineage distinctions needed to prevent confusion.