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.

Chapters20cross-linked references
Protocolv2current P2P generation
Interfaces3RPC, explorer, wallet gateway
Statusαtestnet and devnet only

Browse the reference

From first process to final byte.

20 chapters

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.

  1. 01
    Consensus and runtime source

    The Python node and wallet implementation define what this release executes.

  2. 02
    Vectors and negative tests

    Cross-language bytes, signatures, genesis IDs, rejection cases, and invariants make the contract executable.

  3. 03
    This 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.

SubsystemCurrent stateCritical boundary
ConsensusImplemented alphaLinear next-block acceptance; no fork choice or reorganization.
P2P networkProtocol v2No public seeds, durable scoring, Sybil resistance, or headers-first sync.
WalletLocal testnet alphaOne account, local encrypted vault, no hardware isolation or signed installer.
ExplorerAPI + web previewIndexed history requires the optional SQLite projection and a public API deployment.
MainnetFail-closedNo audited genesis manifest; initialization is intentionally rejected.