Source alphaTestnet only

Built to make the machinery visible.

Luracoin is a compact educational blockchain project: not a token sale, not an investment, and not a finished monetary network.

The idea

Learning improves when the entire path fits in your head.

Many blockchain tutorials stop at a hash-linked list. Production networks, meanwhile, are too large to understand in one sitting. Luracoin sits between those extremes.

It implements real signed bytes, account state, proof of work, persistence, a mempool, peer handshakes, synchronization, a local wallet boundary, and read-only exploration—while keeping the source approachable.

One coherent stack

Every layer has a narrow job.

01Wallet

Creates or restores one address, encrypts recovery material, signs locally, and speaks to a loopback bridge.

Electron · React · secp256k1
02Reference node

Validates blocks and account transitions, persists the chain, exposes private operations, and coordinates peers.

Python · RocksDB · Redis
03P2P network

Performs a chain-aware v2 handshake, announces inventory, relays transactions, and downloads sequential blocks.

TCP · 24-byte envelope
04Explorer

Reads canonical state from one node through a separate public API, with optional SQLite feeds and aggregates.

Astro · Read-only API

Project state

Useful alpha, unfinished network.

The implemented path is suitable for development, tests, and controlled peer experiments. It is not a safe public economy.

Linear PoW consensus and account stateImplemented and covered by tests.
P2P v2 and sequential synchronizationImplemented for same-version peers.
Local wallet RPC and browser gatewayLoopback-only and authenticated.
Public explorer API and UIAPI and index are being completed; UI supports preview mode.
Fork choice and reorganizationsNot implemented; a release blocker for real finality.
Public testnet infrastructureNo stable seeds or faucet are deployed.
MainnetIntentionally blocked with no genesis manifest.

Project principles

What guides the work.

State limits plainly

“Alpha”, “accepted”, “confirmed”, “ready”, and “connected” mean different things. The interfaces should never collapse them into a false promise.

Keep private paths private

The wallet RPC stays on loopback with a bearer. Public exploration is read-only and separately designed.

Prefer executable truth

Binary vectors, tests, and source define interoperability. Marketing copy follows implementation, not the other way around.

Fail closed

Mainnet cannot be activated accidentally. Wrong networks, invalid bytes, unsafe RPC binds, and incompatible data are rejected.

Source publication

One project, released in stages.

The earlier Python prototype is public. The current reference alpha, wallet, and website source are still being prepared for publication.