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 chain and native coin intended to continue the enforcement branch through a BLAKE2b implementation based on Bitcoin Knots.

The BLAKE2b pull request, opt-in unified signature-hash pull request, and tagged testnet release candidates are distinct sources. RC2 coupled several changes at one testnet height. A mainnet release may have a different composition.

Source library

Primary evidence

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

01Official BIP 110 specificationProposal text, status, changelog, and deployment rules02BIP 110 discussionBitcoin development mailing-list discussion03BIP 110 test vectorsOfficial repository vectors for the proposal04BLAKE2b proof-of-work implementationBitcoin Knots pull request #35905Unified signature-hash implementationBitcoin Knots pull request #35706SHA-256d enforcement-branch explorerObserved chain blocks and timestamps07Bitcoin Knots RC2 source tagSigned testnet4 release-candidate source08BLAKE2b testnet4 mining guideIndependent test record and operational warnings09BLAKE2b-capable DATUM GatewayMining job construction and hardware-profile support10Chain-split Lightning risk analysisOperational analysis for Lightning channels

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 downloads.

  • 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.