obtcd
Node implementation: OBTC network parameters, expiry index, REAP validation, replay protection, mining template behavior, and node RPC surfaces.
github.com/organicbitcoin/obtcdOBTC protocol / public source
Bitcoin made digital scarcity possible. OBTC asks whether digital scarcity can remain sustainable over centuries. Through UTXO lifecycle management, renewal, and REAP, it keeps monetary ownership active, funds the long-term PoW security budget, and makes the cost of permanent state explicit.
Repositories
These are the main public references for protocol review, node operation, wallet review, and testnet reproduction. Limited reviewer onboarding is available by invitation, with manual test coin issuance and no public faucet.
Node implementation: OBTC network parameters, expiry index, REAP validation, replay protection, mining template behavior, and node RPC surfaces.
github.com/organicbitcoin/obtcdWallet implementation: network selection, expiry inspection, manual renewal, batch renewal, auto-renew scheduling, and wallet automation surfaces.
github.com/organicbitcoin/obtcwalletProtocol surface
OBTC keeps the UTXO model, then adds lifecycle rules and wallet-facing renewal machinery so dormant state, ownership activity, and PoW security-budget support are handled explicitly.
A UTXO is created and receives an expiry height derived from its creation height.
The holder can spend or renew before expiry; the active path remains explicit.
After the window, ordinary spending closes and the output becomes a REAP candidate.
REAP processes expired outputs under deterministic ordering, input caps, and accounting rules.
Reading
Article
The consolidated explanation of active ownership, the organic thesis, lifecycle rules, renewal, and REAP boundaries.
Open articleDocs
A compact entry point for node operation, wallet preview boundaries, protocol review notes, and candidate parameters.
Open docsWallet
The current wallet surfaces for expiry visibility, renewal, batch operations, and controlled automation.
Open wallet pageReview
Open pressure-test questions around ownership, REAP complexity, bugs, reorg incentives, state, and scalability.
Open review themesDesign notes
Threat-model notes for deterministic ordering, input caps, accounting, MEV, and state-bloat risks.
Open REAP notesReference
The current V1 draft with implementation-aligned parameters, security model, glossary, and FAQ.
Open whitepaper