Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£857.29
EST. MONTHLY
206
DAYS
EST. ROI
This guide explains Bitcoin Core 0.18.0 release 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.18.0 introduced important PSBT, descriptor and operational interfaces while tightening RPC exposure and mining-template expectations. It also removed legacy account APIs and signrawtransaction, changed the supplied systemd data directory and documented a multiwallet coin-control GUI issue.
- Why it matters: Bitcoin Core 0.18.0 was operationally broad: safer deployment required reviewing mining requests, network exposure, service paths, wallet routing and every client that depended on retired RPCs.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core 0.18.0 release in simple English
Bitcoin Core 0.18.0 release: Verify signed binaries, stop cleanly, back up wallets and configuration, record tip and indexes, then test peers, mining, RPC binding, wallets, PSBTs, descriptors and rollback on representative hosts.
Simple example
A node operator is checking Bitcoin Core 0.18.0 release. Check space, ownership and the effective process command before migration. The supplied systemd unit moved data to /var/lib/bitcoind and command-line datadir overrides could outrank bitcoin.conf.
Key terms in plain English
- 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.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- PSBT:
- A portable format for passing an unsigned or partly signed Bitcoin transaction between tools and signers.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Mining boundary
getblocktemplate now failed when the segwit rule was omitted, preventing miners from silently building lower-reward templates. Pool integrations had to declare support and verify live templates.
RPC hardening
rpcallowip no longer implied listening on every interface; rpcbind selected listeners. Public RPC remained unsafe. Hash characters in rpcpassword became startup errors because they were ambiguous with comments.
Service paths
The supplied systemd unit moved data to /var/lib/bitcoind and command-line datadir overrides could outrank bitcoin.conf. Check space, ownership and the effective process command before migration.
PSBT and descriptors
New analyzepsbt, joinpsbts, utxoupdatepsbt, deriveaddresses and getdescriptorinfo expanded offline workflows. Treat descriptors and enriched PSBTs as sensitive topology data.
Removed interfaces
The account API, signrawtransaction and addwitnessaddress were removed; generate was deprecated. Inventory every client and monitoring script for these calls before cutover.
Wallet warning
The release warned that coin-control state could persist incorrectly when switching among multiple GUI wallets. Avoid that combination and test exact wallet routing in automation.
Upgrade evidence
Verify signed binaries, stop cleanly, back up wallets and configuration, record tip and indexes, then test peers, mining, RPC binding, wallets, PSBTs, descriptors and rollback on representative hosts. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of Bitcoin Core 0.18.0 release?
Bitcoin Core 0.18.0 release: Verify signed binaries, stop cleanly, back up wallets and configuration, record tip and indexes, then test peers, mining, RPC binding, wallets, PSBTs, descriptors and rollback on representative hosts.
For Bitcoin Core 0.18.0 release, what should a beginner know about mining boundary?
getblocktemplate now failed when the segwit rule was omitted, preventing miners from silently building lower-reward templates.
For Bitcoin Core 0.18.0 release, what should a beginner know about rpc hardening?
rpcallowip no longer implied listening on every interface. Rpcbind selected listeners. Public RPC remained unsafe.
For Bitcoin Core 0.18.0 release, what should a beginner know about service paths?
The supplied systemd unit moved data to /var/lib/bitcoind and command-line datadir overrides could outrank bitcoin.conf.
Conclusion
Bitcoin Core 0.18.0 was operationally broad: safer deployment required reviewing mining requests, network exposure, service paths, wallet routing and every client that depended on retired RPCs.
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.