Skip to content
RunlaiDengPublic

About

RLDCOIN protocol development for asynchronous peer-to-peer payments across disconnected regions. No-value testnet candidates; mainnet not launched.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Rldcoin

A clean Rust implementation of Rldcoin: Interstellar Peer-to-Peer Payments. The canonical mechanism paper is spec/WHITEPAPER.md, bound by its publication receipt. The paper's SHA-256 is 30ad8bfeca1a5da98ebd92f5f1acda56348f6d9686508d3da6180c873d4487e8.

RLD is the only native payment and fee currency. The lifetime issuance budget is 21,000,000 RLD, with 10^24 atomic units per RLD and zero initial allocation. Mining and placement use public Argon2id work. A relay acknowledgment, coupon, proof, configuration signature or solved hash does not itself issue money.

This repository was rebuilt from an empty worktree. The former implementation and private state were moved to the owner's macOS Trash. Existing remote Git history is preserved; no legacy ledger or key migration is supported.

Build

Install Rust 1.98.0 and the official RISC Zero Rust guest toolchain 1.88.0 with rzup install rust 1.88.0. The monetary proof profile pins RISC Zero 3.0.6. Building the local prover also requires CMake and platform C++ tools. On macOS, install Xcode and its Metal toolchain. The build helper explicitly selects Metal 3.1 for the pinned vendor kernels when the installed compiler defaults to Metal 4; it does not modify vendor sources or skip kernels.

# macOS, including both real guest programs and local succinct prover
./tools/build-macos.sh

# Linux with its standard C++ build toolchain
cargo build --release --workspace --locked

# Command descriptions; these do not start a network
./target/release/rld --help
./target/release/rld-prover profile

rld-prover profile prints the actual compiled native/controller image IDs and verifier commitments. A currency descriptor must use this exact profile. Native and controller receipts are real succinct receipts; development/fake receipts and unresolved assumptions are refused. Changing the guest relation changes its image ID and requires a distinct explicitly approved currency descriptor.

The host pins the reviewed real proof profile in spec/EXECUTABLE_PROFILE.json. rld profile reports its native/proof source binding and expected programs. Node initialization, cold opening, descriptor construction and monetary CLI currency reads refuse a different program profile. A mismatching old store remains unchanged and needs its matching historical release; this is not a monetary upgrade/migration command.

For an authorized native/proof source revision, first build the real prover from that source (cargo build --release -p rld-prover --locked, using the macOS helper where needed), then run python3 tools/pin-executable-profile.py. Review that public binding, build the complete workspace and compare rld profile with the actual rld-prover profile. The node build script rejects stale native/proof source fingerprints. Pinning alone is not verification that a stale prover was rebuilt or that a Linux build reproduces the same image; those comparisons remain required release evidence. The existing CI compiles the committed binding.

Components

  • crates/protocol: canonical CBOR, monetary types, counted prefix-map proofs, exact issuance work, native transitions, independent terminal controllers, authentication, succession and recursive verification relations.
  • crates/node: durable replay, encrypted local signing custody, PBFT, signed and pinned-TLS contact carriage, bounded fragments, offline bundles, public signed-operation API, disk-resident verified native-history and execution-receipt indexes, independently scheduled bounded proving lanes (including recursive Mint index correspondence), disk state material and certified historical membership/absence queries. Native state uses shared immutable value and commitment paths. Controllers, conflict records, Mint facts, acceptance covers, historical fee policies, receiving families, service contracts, coupon uses, the UTXO map, operation map and five permanent decision/birth/funding maps execute through private disk adapters; indexed guest inputs authenticate UTXO, operation-log and five permanent-map accesses, plus controller/conflict, service/coupon replacement and family/acceptance/fee accesses, with Mint event/slot reads and appends when the exact correspondence certificate is available; other state collections still require complete execution material.
  • crates/cli: wallet signatures and balances, ordinary CPU mining, placement work, payment/service/family drafts, evidence extraction, operator tools, cancellation and disconnected carriage.
  • methods: actual RISC Zero native and controller guest programs.
  • crates/prover: local proof generation and final independent verification before releasing the receipt.

See operator instructions, implementation boundaries and the initial build record. Later source-bound compile receipts live in docs/builds/; they do not retroactively qualify earlier source.

Current boundary

This is an experimental implementation, not a launched monetary network. No network keys or genesis were generated during this rebuild. No old balances or keys are imported. Compilation is not runtime verification or a security audit. The owner requested source review and compilation without a new local test campaign. Sustained capacity, complete large-history storage, independent key custody, physical stellar links and mainnet operation remain unqualified.

About

RLDCOIN protocol development for asynchronous peer-to-peer payments across disconnected regions. No-value testnet candidates; mainnet not launched.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages