How it works
Local trust. A longer reach.
Interstellar distance changes the problem. Rldcoin is designed around separate regions that verify locally and communicate asynchronously.
01 / THE ZONE
A local ledger.
Its own consensus.
A Zone maintains a ledger and local consensus. Its participants confirm local activity without waiting for a distant star system. The architecture is intended to support regions that cannot depend on an always-reachable Earth clearing service.
A Zone could one day serve a community, a habitat, or a spacecraft. Earth is the first deployment; future regions need their own operational and security qualification.
Earth
The beginningA habitat
A future regionA distant settlement
A future region02 / THE JOURNEY
A transfer carries evidence.
Each step establishes what the next region is allowed to accept. Explore the intended lifecycle below.
Lock at the source
The sender authorizes a transfer. The source Zone finalizes it and locks the asset, so it cannot be spent there again.
Explore the intended transfer lifecycle. This diagram does not submit a transaction.
03 / THE INVARIANTS
What distance
must never change.
Authorization
A sender must authorize the transfer. Possession of a copy of the ledger does not confer ownership.
A single spendable location
The source locks the asset before export. The destination accepts it only after verifying the required evidence.
Explicit uncertainty
Missing, conflicting, or unsupported evidence leaves a transfer pending or quarantined. A timeout is not proof that the destination did not import it.
Continuous history
Upgrades, recovery, and changes in cryptography must preserve the established history and asset lineage.
Distance still takes time.
No protocol removes the need for information to arrive. A local confirmation, an exported proof, a destination import, and a returned receipt are different events.
The next step is understanding.
Explore the ideas and evidence behind Rldcoin.