The Luracoin technical reference
One source of truth for the entire stack.
Operate the software, implement the wire formats, reason about consensus, integrate the APIs, and understand every current security boundary. This documentation follows the executable 0.1.0 alpha source.
Browse the reference
From first process to final byte.
20 chapters
Install dependencies, start a testnet node, open the wallet, and verify the stack.
Read chapter →Full node operationsRun, configure, isolate, inspect, back up, and troubleshoot a full node.
Read chapter →Wallet operationsCreate, restore, lock, receive, sign, send, and understand the wallet trust boundary.
Read chapter →The consensus surface, network namespaces, lifecycle, and normative language.
Read chapter →Addresses & keysBIP39, BIP32 root derivation, secp256k1 keys, HASH160, and Base58Check addresses.
Read chapter →TransactionsCanonical 85/213-byte encoding, signing, IDs, coinbase, nonces, and validation.
Read chapter →Blocks & validationHeader encoding, canonical block hash, validation order, state transition, and size schedule.
Read chapter →PoW, difficulty & emissionCompact targets, retarget arithmetic, mining loop, subsidy halvings, and tail emission.
Read chapter →State, mempool & storageAccount state, Redis admission, RocksDB indexes, block files, idempotence, and crash recovery.
Read chapter →Authenticated loopback endpoints, schemas, cursors, readiness, receipts, and errors.
Read chapter →Explorer APIPublic read-only endpoints, response models, pagination, capabilities, and errors.
Read chapter →Explorer operationsEnable the SQLite projection, monitor backfill, rebuild safely, and connect the website.
Read chapter →Process boundaries, data flows, canonical stores, derived views, and component ownership.
Read chapter →Security & limitationsThreat boundaries, implemented hardening, known gaps, and public-network blockers.
Read chapter →Testing & interoperabilityExecutable vectors, cross-language conformance, negative tests, CI, and change discipline.
Read chapter →Canonical table of network IDs, ports, byte limits, timing, economics, and service bounds.
Read chapter →GlossaryPrecise meanings for Luracoin protocol, node, wallet, and explorer terminology.
Read chapter →Migration & compatibilityProtocol v2 boundaries, clean data directories, compatibility rules, and upgrade checklist.
Read chapter →How to read this documentation
Truth has an explicit order.
Luracoin is still an alpha. The documentation is detailed, but it never outranks the executable behavior that nodes actually validate.
- 01Consensus and runtime source
The Python node and wallet implementation define what this release executes.
- 02Vectors and negative tests
Cross-language bytes, signatures, genesis IDs, rejection cases, and invariants make the contract executable.
- 03This documentation
The human model, runbooks, schemas, rationale, risks, and integration guidance live here.
Implementation boundary
What exists today.
No roadmap feature is presented as an implemented guarantee.
| Subsystem | Current state | Critical boundary |
|---|---|---|
| Consensus | Implemented alpha | Linear next-block acceptance; no fork choice or reorganization. |
| P2P network | Protocol v2 | No public seeds, durable scoring, Sybil resistance, or headers-first sync. |
| Wallet | Local testnet alpha | One account, local encrypted vault, no hardware isolation or signed installer. |
| Explorer | API + web preview | Indexed history requires the optional SQLite projection and a public API deployment. |
| Mainnet | Fail-closed | No audited genesis manifest; initialization is intentionally rejected. |
