A little more understanding.

Rldcoin’s long-term goal is peer-to-peer payments between future human communities across star systems. It aims to preserve ownership and a continuous asset history across Earth, space habitats, spacecraft, and distant settlements. The permanent Earth network is the first step; interstellar payment routes are not deployed.

No. The permanent Earth network was established on September 22, 2026. It has a published genesis identity and retained history. Earth now uses explicitly adopted regional proof-of-work rules for automatic mining and signed local transfers. The original genesis and certified heartbeat history remain published. Development networks and simulations are separate from this permanent identity.

The Earth node accepts valid signed local transfers of mature RLD. Mining rewards mature after 100 additional blocks. The current release is a command-line node and developer transaction API; a consumer wallet is still to come. This website offers no token sale or exchange.

A signed transfer can be accepted by the current node quickly, but that only makes it pending. The target is one block every ten minutes on average; the first on-chain confirmation can arrive sooner or later, and a stronger chain can still replace it. The 100-block maturity rule applies to newly mined rewards, not ordinary transfers. Rldcoin aims for a separately qualified, prefunded payment layer that gives a verifiable local receipt within seconds. That layer and a consumer wallet are not available today.

The fixed supply is 100,000,000,000 RLD. One RLD contains 10²⁴ runlai, the smallest unit. The PoW adoption moves the original unused service reserves into one unissued mining reserve, with no personal allocation. Miners earn new RLD only through valid work on the selected chain. Creating a Zone or copying a ledger does not create more RLD.

There is no personal or founder genesis allocation and no reserved founder share. The launch operator and later miners follow the same public work, reward, and maturity rules. Early mining before wider participation can concentrate ownership; no participant is guaranteed a share. Community contributions to source review, verification, documentation, and protocol development are welcome.

Run the released node with mining enabled and your receiving public key. It automatically searches for SHA-256d blocks. Valid blocks on the selected greatest-work branch earn a subsidy and included fees. The initial subsidy is 250,000 RLD, with a ten-minute target interval and a 200,000-block reward era. Actual rewards depend on competition and luck; discarded-branch rewards disappear.

A Zone is a region with its own ledger and local consensus. The planned architecture would confirm activity within each Zone locally, while transfers to another Zone travel asynchronously. A future Zone could serve a community, habitat, or spacecraft. Only Earth is currently deployed; cross-Zone transfers are disabled.

No. Information still has to reach its destination. The design separates local confirmation from the time needed to deliver a cross-Zone proof. The destination must verify and finalize the import before the recipient can spend the asset there.

The design keeps a transfer in an explicit pending state until the necessary evidence arrives. The source locks the asset before export; the destination verifies it before import. Elapsed time alone cannot unlock the source balance, because that could let the same asset be spent twice.

The current launch is controlled by one owner across two hosts. Separate processes or machines do not establish independent governance. Independent miners, broader hash-power distribution, and independent security review remain important next steps. Anyone adopting the published PoW rules can validate and mine without the founder’s signing keys.

The network page links to the exact genesis manifest, signed declaration, authorization records, checksums, and the versioned public release. Compare artifacts against the published manifest commitment. An external timestamp records the existence of the genesis file; it is not an independent security audit.

Read the architecture, inspect the published source and evidence, reproduce verification work in an isolated environment, and discuss implementation questions in the community forum. You can also build the released node, verify the pinned adoption, connect to the public Earth peer, and enable mining with your own receiving key. Running a node alone does not guarantee a block reward.