Settle where you are
Owners authorize exact payments. An accepted local quorum orders them. Communities with locally homed funds can trade during isolation while their own quorum and resources remain available.
RLDCOIN / FOR THE FUTURE OF HUMANITY
Interstellar peer-to-peer payments.
For humanity’s future.
One currency for separated worlds. Settle nearby in runlai (RLD). Carry verified payments farther when contact becomes possible.
Research construction · No active mainnet · Existing test assets have no monetary value
THE IDEA
A local purchase should not
wait for a distant world.
Communication across space is delayed and intermittent. Rldcoin gives each balance one authoritative home: local communities settle distinct funds locally, then move exact payments between homes without copying the spending right.
Prepare to send farther
Arrange receiving capacity before choosing future inputs. Prepare exact funds locally; an independent controller cancels or releases while other local settlement continues.
Receive, then keep trading
A complete released payment travels through real contacts. After verification and one-time import, the recipient can spend locally without a message returning to the source.
RUNLAI / RLD
One currency.
A finite beginning.
Payments, fees and native services use RLD under one monetary identity. Moving between domains neither wraps the currency nor creates another supply.
21 million RLD
The proposed lifetime cap. Public work consumes unique issuance slots once; new domains cannot enlarge the budget.
Zero initial allocation
No spendable genesis, founder reserve, investor, treasury or validator allocation.
Public issuance work
Installed grants support local Mint work without prior RLD or a compulsory pool. Work distributes issuance; it does not grant consensus votes.
THE WHITE PAPER
A mechanism for
the long journey.
Money, local authority, prepared transfers and the conditions that keep them meaningful.
The paper follows a payment from owner authorization to independent verification and destination receipt. It explains finite receiving capacity, cancel-or-release controllers, public-work issuance, accepted authority exposure and durable carriage.
Distance, authority failure and missing data remain explicit. Before release, certified cancellation can return prepared escrow. After release, only permanent destination rejection permits recovery; silence cannot refund a payment.
OPEN DEVELOPMENT
Read the design.
Inspect what exists.
The current paper is a research construction. Executable implementation, measured performance and independent security need their own evidence. Existing no-value candidates keep their separate scope.
Development stage
No mainnet or operational interstellar payment route is established. Read the distinction between publication, implementation and qualification.
Network & developmentSource and review
Inspect the node implementation and its source-specific requirements, limits and development records.
Browse protocol sourceBuild with us
Contribute mechanism review, implementation or clear documentation. Tie each claim to the exact work it describes.
Developer resources