1. INTRODUCTION - WHY BITCOIN PURITY?Bitcoin Purity is an open-source, SHA-256d proof-of-work blockchain and full-node implementation focused on one principle: Bitcoin should remain peer-to-peer electronic cash, with the base layer primarily dedicated to monetary transfers rather than general-purpose data storage.
The project is built from Bitcoin Knots and follows the BIP110/Reduced Data enforcement-chain history. Its mainnet launched on 19 August 2026, with a hardcoded Purity activation at block 961637. Bitcoin Purity permanently enforces Reduced Data (RDTS) consensus restrictions, uses a 24-hour ASERT difficulty adjustment and retains Bitcoin's SHA-256d proof of work and transaction formats.
An important distinction: the project does not describe itself as an independently issued token or a new ticker. Its stated objective is continuity with Bitcoin under different consensus rules. Marketplaces and third-party mining services commonly use
BTC1 as an identifier for the Purity chain; that identifier is not presented as a newly created protocol-native asset in the official documentation. Bitcoin Purity and the BTC-majority chain nevertheless have divergent post-fork histories.
2. NETWORK & TECHNICAL SPECIFICATIONSProject Bitcoin Purity
Mainnet announcement 19 August 2026, 10:00 UTC
Activation height 961637
Proof of work SHA-256d
Target block interval 600 seconds (~10 minutes)
Difficulty adjustment ASERT (aserti3-1d)
ASERT half-life 24 hours
ASERT anchor Block 961632 (BIP110 enforcement chain)
Consensus foundation Bitcoin Knots v29.4.knots20260508
Reduced Data rules Permanent BIP110/RDTS at activation
Deep-reorg mitigation Park reorgs deeper than 6 blocks by default*
Transaction formats Bitcoin-compatible
Replay protection None (by design)
Default Bitcoin P2P port 8333
P2P message magic f9beb4d9
Current stable release v1.0.2 (as checked 22 Oct 2026)
License MIT
0000000000000000003ea74f4dafdda7ed4e02c4c1ccb9768e0ca4f9e1a35159
- SHA-256d proof of work and Bitcoin's target block spacing.
- Bitcoin addresses, transaction serialization and signature hashing (sighash).
- Inherited transaction history before the chain divergence; no independent new-coin genesis distribution.
- Standard node binaries: bitcoind, bitcoin-qt and bitcoin-cli.
What changes in Purity?- Permanent BIP110/RDTS: consensus rules constrain unnecessary arbitrary-data payloads and certain script constructions rather than relying only on configurable mempool policy. For example, the current specification caps OP_RETURN outputs at 83 bytes and non-empty non-OP_RETURN output scripts at 34 bytes.
- ASERT difficulty adjustment: block-by-block retargeting designed to respond to changes in available hash power; the 10-minute interval remains a target, not a guarantee.
- Deep-reorganization parking: nodes ordinarily pause automatic reorganizations deeper than six blocks for local operator review.
Detailed rules and the actual implementation are authoritative:
Consensus specification.
3. CODE, RELEASES & WHITEPAPERPlease obtain software through official project pages, verify available checksums and independently review source code whenever practical.
4. MINING - SHA-256 HARDWARE WELCOMEBitcoin Purity retains SHA-256d. SHA-256 ASIC hardware, including compatible home-mining devices such as Bitaxe, can participate. Both hosted mining and self-hosted node-based mining are available. Expected earnings and solo-block probabilities depend on changing difficulty, hashrate, fees and luck: no mining income is guaranteed.
Official trial SOLO pool (
monitor):
High-hashrate miners: stratum+tcp://pool.bitcoinpurity.org:3333
Low-hashrate miners: stratum+tcp://pool.bitcoinpurity.org:4444
:
Main: stratum+tcp://smartpool-a.bitcoinpurity.org:3333
Backup: stratum+tcp://smartpool-b.bitcoinpurity.org:3333
Emergency: stratum+tcp://smartpool-a.bitcoinpurity.org:3433
Bitcoin Purity supports an embedded DATUM gateway for Stratum V1 hardware. The documented default port is 23334; it is local-only by default and must be secured before binding to a LAN interface.
Independent community pool options (third-party operators; verify pool terms and live status):
Complete official miner guide: bitcoinpurity.org/miners.html. Confirm payout address format, worker name, Stratum settings and fees with the specific pool before starting.
5. WALLETS, NODES & EXPLORERSBitcoin Purity node / desktop wallet: official
run-a-node instructions, binaries and source code are linked above.
PurityWallet for Android: the project lists
PurityWallet 1.0.0. Use its official APK and verify the accompanying SHA256SUMS before installation.
External wallet support: BlueWallet and compatible Sparrow versions can connect using a custom Purity Electrum server. Follow the official compatibility guidance:
Wallet connection instructions.
Electrum host: electrum.bitcoinpurity.org
Port: 50002
TLS / SSL: Enabled
BlueWallet: electrum.bitcoinpurity.org:50002:s
- the rich list tracks value created after the fork, not all pre-fork Bitcoin balances.
Important wallet warning: the same address/transaction formats do not mean that spending is risk-free across divergent chain histories. Read the replay and settlement guidance below before transferring value.
6. TRADING AND THIRD-PARTY SERVICESOne independent trading venue currently displaying Bitcoin Purity under the
BTC1 market identifier is
NestEx (BTC1/USDT).
Listing by a third party does not imply project endorsement, reliable liquidity, low counterparty risk or recognition of BTC1 as an official protocol ticker. Review deposits, withdrawals, confirmations, order-book liquidity, custody and exchange terms yourself. Exchange listings may change; check the venue directly.
7. CURRENT IMPLEMENTATION VS FUTURE RESEARCHPresent in the current project tree:- Permanent Reduced Data / BIP110 rules.
- SHA-256d mining with ASERT 24-hour difficulty adjustment.
- Configurable local deep-reorg parking.
- Full-node software, wallets, explorers and mining infrastructure as linked above.
Documented future research directions, not active consensus rules:- SEAL-2 block headers.
- Possible Taproot removal and further SegWit changes.
- Post-quantum signatures and larger blocks (32 MB proposal).
Not implemented: automated freezing of double-spend coinbases/inputs is described in project materials but is not an operational security mechanism. These future items have no committed activation schedule. See the
official roadmap.
8. SECURITY, REPLAY & NETWORK RISKSBitcoin Purity intentionally does not add transaction-level replay protection. Since addresses, transaction formats and sighash remain compatible, a transaction may be valid on both the Purity and legacy histories, depending on each chain's current state and rules. Treat cross-chain spending as a technical operation requiring special care.
The network's available SHA-256d hash power can fluctuate. Reduced hash rate increases exposure to censorship, chain reorganizations and double-spend attempts. Six-block reorg parking is
local policy, not a promise of chain finality or protection against every 51% attack. Avoid treating zero-confirmation or lightly confirmed payments from untrusted parties as final; use conservative confirmation policies for valuable transactions.
Read before using funds: Official safety guidance |
FAQ.
9. COMMUNITY & CONTACTWe welcome technically rigorous discussion: node operators, miners, wallet developers, pool operators and Bitcoin users are invited to review the code, test the software, identify weaknesses and contribute constructive feedback. The most useful support for a new network is not price speculation, but independent verification, reliable infrastructure and an informed community.
