For developers
Build for what comes next.
The protocol is open to inspection. Start with the exact source, follow the evidence, and help turn long-term requirements into verifiable engineering.
THE STACK
Rust at the core.
Evidence throughout.
The published release includes protocol source, operating material, verification tools, and versioned genesis artifacts.
# From the published source archive
# Requires the pinned Rust toolchain
cargo build --locked --release -p rld-pow
cargo test --locked --release -p rld-pow
# Follow NODE-GUIDE.md in the release to joinBuild and test locally, then follow the release’s node guide to pin the existing network, connect a peer, and enable mining.
rld-coreProtocol types, ledgers, transactions, transfer proofs, and verification.
rld-pow / rldpowAutomatic mining, signed local transfers, durable blocks, greatest-work selection, and peer synchronization.
rld-signer / rld-witnessIsolated signing, durable authorization, state witnessing, and recovery checks.
rld-cli / rld-simCommand-line tools and local scenarios for multi-Zone communication.
vectors / tools / formalTest vectors, verification programs, and formal models.
START WITH VERIFICATION
Useful work starts
with a precise question.
Reproducible findings help the project move forward. Public source availability does not mean the protocol has received an independent security audit.
Reproduce a result
Record the exact release, toolchain, inputs, commands, and output. Distinguish simulations from real network evidence.
Review a boundary
Inspect authorization, duplicate imports, replay, incomplete proofs, and recovery behavior. Use an isolated environment.
Discuss an improvement
Bring a concrete issue or design question to the forum. For vulnerability disclosure, follow SECURITY.md in the source archive.
Every claim should have a record.
Explore the ideas and evidence behind Rldcoin.