Questions before the long journey.

A research construction for interstellar peer-to-peer payments in runlai (RLD). Each balance has one authoritative home. Communities settle locally and move exact payments between homes through prepared, verified transfers.

This publication establishes no active mainnet or consumer payment service. The website offers no token sale, exchange or wallet connection. Existing test assets have no monetary value and never migrate into a monetary genesis.

The proposed lifetime cap is 21,000,000 RLD, with 10^24 atomic units per RLD. Spendable genesis and founder, investor, treasury and validator allocations are zero. No halving, tail emission or lost-money reissue is specified.

There are 4,096 roots of 1,000,000 unique slots. Successful Mint work consumes one eligible slot and pays 0.005126953125 RLD to its work author. All slots together sum to the cap. Claiming or relocating a range creates no RLD and does not replace Mint work.

The construction admits public Mint work under installed grants without prior RLD, stake or a compulsory pool. It proposes Argon2id with 64 MiB, three passes and one lane. A responsive accepted local quorum is still required. CPU admission does not establish profit, equal hardware opportunity or ASIC resistance; no production benchmark is claimed.

No. Public work distributes a conserved issuance budget. Local PBFT uses admitted validators and a stated fault bound to order payments. A work solution neither grants a vote nor selects a global payment history.

No calendar date is promised. The work profile has no automatic retarget. Hardware progress may accelerate issuance, while lost grants or unavailable authority can leave actual issuance below the cap.

It can circulate distinct RLD already homed locally while its accepted local quorum and resources remain responsive. An issuance grant is not needed to pay existing balances. A minority partition cannot finalize. Ships should prepare local funds, custody and receiving arrangements before departure.

Not after compatible receiving capacity is available. A destination preissues a funded coupon for one source, leaving future inputs unspecified. The payer selects inputs locally and can send a released package forward. New sources, unknown destinations or exhausted capacity still need setup.

The native ledger locks the exact escrow and delegates it to an independent one-decision controller. Historical proving can continue while other payments advance. The controller releases only when the required proof and material are ready, or certifies cancellation before release.

Before release, an authorized controller cancellation permits one local return; performed preparation service stays paid. After release, only certified permanent destination rejection permits recovery. Silence, transport expiry, a missing receipt or a deadline cannot refund the released amount. Failed authority can strand funds.

After the destination verifies the complete released package, durably installs current material and finalizes one-time import. The recipient can then pay locally without waiting for a message to return to the source. Transport custody alone grants no balance.

No. A cross-domain payment follows actual communication or carriage opportunities. Local settlement does not wait for a distant vote, but its real latency and proof cost still require measurement. The current construction has no claimed achieved latency or daily volume.

Every owner-initiated local or cross-domain payment includes a positive RLD service fee and a positive share for a verifiable prior Mint work author. Exact authorized existing balances fund them, including any sponsor contribution. Service terms cover consensus, verification and archival reserves; relays and renewal have separately funded contracts.

Not automatically. Acceptance covers define finite authority families and security rules a recipient accepts. Two balances can share the RLD denomination but differ in exposure and acceptance. Signed broadening requires verified inclusion; narrowing needs additional ancestry evidence. An incident can quarantine the entire covered portion.

Counted binary prefix trees commit exact keys and values, branch positions and child counts. Updates share unchanged branches; the root depends on the records, not their insertion order. Membership and adjacent-neighbor absence proofs retain a 64-branch limit. Complete current data, permanent decisions and funded history custody remain necessary; a smaller proof does not supply missing data or establish throughput.

Under a correct authenticated RLD program and a sound proof backend, they establish monetary execution without carrying every historical event. They do not reveal unseen valid quorum forks or supply missing current data. The paper’s reference adapter is not an implemented or independently qualified RLD guest.

Finite signing schedules, retained controller authority, complete current data, permanent decisions, funded archives and authenticated succession all matter. Renewals need resources. No finite reserve funds infinite service, and key or authority loss can halt progress.

Read the paper, inspect the exact implementation and follow its repository instructions. Mechanism review, code and documentation all help. Current experiments remain no-value; a published paper or successful build does not establish monetary adoption, independent security or a physical stellar route.