Network & development
Read the current construction alongside the separately scoped source and no-value network records.
The current paper specifies a research construction. Existing testnets and ground candidates retain separate identities and evidence scopes. Their observations do not establish an implementation of this design.
Content reviewed 20 October 2026. Live telemetry is not fetched here; this summary cannot establish current availability. External status may be stale or unavailable and is an operator observation.
Testnet guide Operator telemetryOne RLD currency and fixed issuance budget; local PBFT settlement; funded receiving capabilities; independent cancel-or-release controllers; one-time import or rejection; recursive execution relations; explicit acceptance covers; finite key, custody and archival obligations. These mechanisms form a conditional research construction.
A complete monetary implementation needs authenticated RLD program and verifier identities, correct executable transitions, durable signing custody and complete current data. Practical proof costs, payment latency, sustained capacity and failure behavior require evidence tied to that implementation. Independent security and physical-route qualification remain separate work.
The site publishes no measured throughput or settlement-time claim for this architecture. Earlier engineering targets and source-bound results retain their own records; they are not measurements of the current construction.
Existing testnets and ground candidates use separate source and protocol identities. Their test assets have no monetary value. Preserve their failures and limits when interpreting a result; neither their balances nor their keys migrate into a monetary genesis. Publishing this website changes no protocol or node service.
An actual launch requires a separately authenticated genesis with zero initial issuance and zero allocation, fresh monetary keys and explicit adoption of the completed executable construction. A website update cannot stand in for those steps.
HISTORICAL PUBLIC EVIDENCE / 4 OCTOBER 2026
These observations concern an earlier regional prototype, not the current paper’s controller construction. Both used the same v53 runtime. Ordinary-cycle success and the subsequent failed fault scope are separate results. Newer local work is outside this publication snapshot.
Twelve local nodes completed Earth–Proxima–Andromeda–Earth while Earth was stopped during the remote legs. Native replay authenticated all twelve journals and recipient observations; issued 300 = liquid 300 + unresolved exports 0.
After contact restoration, the new export was not imported at Proxima height 12 within the declared window. Separate stopped authentication preserved the original owner requests and private state. It neither recovered the run nor changed the failure.
Historical fixture results: same host and controller, no monetary value. These results do not qualify sustained BFT service, independent custody, long history, physical routes or all I1–I12.