Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 136 TxRef in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 136 is a Draft informational proposal for TxRef, a human-friendly Bech32 encoding of a confirmed transaction’s position in the blockchain, optionally including an output index. Unlike a txid, a TxRef has only a weak locational relationship to a transaction and can resolve differently after a reorganisation.
- Why it matters: BIP 136 offers a compact human transaction locator, but its weak link to chain position is fundamentally different from txid identity. Safe use requires maturity, independent resolution and content verification after every lookup.
- Current position: BIP 136 is a Draft informational proposal for TxRef, a human-friendly Bech32 encoding of a confirmed transaction’s position in the blockchain, optionally including an output index.
BIP 136 TxRef in simple English
BIP 136 TxRef: A TxRef encodes coordinates that locate a transaction within a block, not a cryptographic digest of transaction bytes.
Simple example
A node operator is checking BIP 136 TxRef. If chain history changes, the same coordinates may be empty or refer to something else. Applications must fetch and verify the resulting transaction against independent expectations.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Position, not identity
A TxRef encodes coordinates that locate a transaction within a block, not a cryptographic digest of transaction bytes. If chain history changes, the same coordinates may be empty or refer to something else. Applications must fetch and verify the resulting transaction against independent expectations.
Bech32 transport properties
The encoding uses a human-readable prefix, restricted character set and checksum for transcription resistance. A valid checksum detects many errors but does not authenticate chain data or provider responses. Network prefix and format version remain mandatory validation fields.
Maturity recommendation
The BIP recommends at least 100 blocks of maturity to reduce reorganisation risk. That is a risk threshold, not finality or a consensus guarantee. Higher-value or adversarial applications may require stronger evidence and continued monitoring after resolution.
Outpoint references
An optional output index can identify a particular transaction output. The resolver must confirm that the index exists and that script and value match the intended contract. A location resolving successfully is not enough to authorise payment or spending.
Lookup architecture
A full node without a transaction index may need block position data or an external index to resolve efficiently. Third-party resolvers create availability and deception risk. Query at least an independently validating source and verify block header, chainwork and transaction Merkle inclusion.
Draft and interoperability
BIP 136 remains Draft. Implementations may support different versions, prefixes or presentation conventions. Pin the exact BIP revision and official test vectors, and avoid making TxRef the only recovery reference for funds or legal records.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is the main point of BIP 136 TxRef?
BIP 136 TxRef: A TxRef encodes coordinates that locate a transaction within a block, not a cryptographic digest of transaction bytes.
For BIP 136 TxRef, what should a beginner know about position, not identity?
A TxRef encodes coordinates that locate a transaction within a block, not a cryptographic digest of transaction bytes.
For BIP 136 TxRef, what should a beginner know about bech32 transport properties?
The encoding uses a human-readable prefix, restricted character set and checksum for transcription resistance.
For BIP 136 TxRef, what should a beginner know about maturity recommendation?
The BIP recommends at least 100 blocks of maturity to reduce reorganisation risk.
Conclusion
BIP 136 offers a compact human transaction locator, but its weak link to chain position is fundamentally different from txid identity. Safe use requires maturity, independent resolution and content verification after every lookup.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.