Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£852.00
EST. MONTHLY
207
DAYS
EST. ROI
This guide explains Bitcoin Core 0.13.1 in plain English. It summarises the important changes, who they affect and what should be checked before an upgrade.
TL;DR
- What it is: Bitcoin Core 0.13.1 was released on 27 October 2016 with mainnet activation parameters for the Segregated Witness soft fork, the associated NULLDUMMY rule, bug fixes and performance improvements. It also dropped OS X 10.7 support.
- Why it matters: Bitcoin Core 0.13.1 supplied the activation-aware implementation for SegWit and NULLDUMMY. Safe operation required chain-state monitoring, miner-wide template testing and a platform- and wallet-aware rollback.
- Current position: Bitcoin Core 0.13.1 was released on 27 October 2016 with mainnet activation parameters for the Segregated Witness soft fork, the associated NULLDUMMY rule, bug fixes and performance improvements.
Bitcoin Core 0.13.1 in simple English
Bitcoin Core 0.13.1: OS X 10.7 was no longer supported, while 0.13.0 had been unreliable there. Operators had to confirm host support, verify release artefacts and stop cleanly.
Simple example
A node operator is checking Bitcoin Core 0.13.1. Nodes tracked signalling before lock-in and activation. SegWit used BIP 9 version bit one with a defined start date and retarget-period threshold.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Soft fork:
- A proposed tightening of Bitcoin rules that old nodes may not enforce themselves.
Activation parameters
SegWit used BIP 9 version bit one with a defined start date and retarget-period threshold. Nodes tracked signalling before lock-in and activation. A node running 0.13.1 understood the rules, but activation state depended on the chain. Dashboards needed state and height, not just software version.
SegWit validation benefits
The release notes described stable txids for witness changes, block weight, improved sighash scaling, signed input values and stronger script hashes. Each benefit applied under specific spend and activation conditions. Legacy transactions and wallets did not automatically gain every property.
NULLDUMMY
BIP 147 converted the long-standing null dummy relay policy for CHECKMULTISIG into consensus at SegWit activation. This removed one transaction-malleability vector for both legacy and witness spends. Script test fixtures needed valid and non-null dummy cases across policy and block validation.
Mining readiness
Pools needed compatible getblocktemplate handling, signalling policy, witness commitments and compact-block relay with witness transactions. Every template producer and standby mattered. A single obsolete failover could mine invalid or non-signalling work after an incident.
Wallet and RPC changes
The release included witness wallet fixes, address-book handling, a hexadecimal RPC cookie and deprecation of getinfo. It removed createwitnessaddress and tightened importprunedfunds arguments. Integration tests needed exact method and serialization expectations, not broad SegWit smoke tests.
Platform and upgrade boundary
OS X 10.7 was no longer supported, while 0.13.0 had been unreliable there. Operators had to confirm host support, verify release artefacts and stop cleanly. Wallet backups and chainstate compatibility remained part of rollback planning.
Historical status
SegWit later activated, but 0.13.1 is now obsolete. An archival test should reconstruct BIP 9 transitions and witness templates on an isolated chain. Current production nodes need supported releases and contemporary peer, wallet and security guidance.
Frequently asked questions
What is the main point of Bitcoin Core 0.13.1?
Bitcoin Core 0.13.1: OS X 10.7 was no longer supported, while 0.13.0 had been unreliable there.
For Bitcoin Core 0.13.1, what should a beginner know about activation parameters?
SegWit used BIP 9 version bit one with a defined start date and retarget-period threshold.
For Bitcoin Core 0.13.1, what should a beginner know about segwit validation benefits?
The release notes described stable txids for witness changes, block weight, improved sighash scaling, signed input values and stronger script hashes.
For Bitcoin Core 0.13.1, what should a beginner know about nulldummy?
BIP 147 converted the long-standing null dummy relay policy for CHECKMULTISIG into consensus at SegWit activation.
Conclusion
Bitcoin Core 0.13.1 supplied the activation-aware implementation for SegWit and NULLDUMMY. Safe operation required chain-state monitoring, miner-wide template testing and a platform- and wallet-aware rollback.
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.