What is available.
| Surface | State | Meaning |
|---|---|---|
| Native application | Local research | Development implementation and local checks. |
| Independent validator network | Unverified | No completed actual-engine result established. |
| Public testnet / mainnet | Not launched | No public transaction service offered. |
| Browser account experience | Illustration | Local interface model; no ledger connection. |
| Dollar backing / cash / cards | Not offered | No issuer or bank program represented. |
| Public token sale | None | No purchase or investment flow. |
The next decisive result.
Actual validator processes must commit native transactions and supply evidence that an independent client can verify. That remains the network acceptance gate.
Local application checks and synthetic signed fixtures support development, but cannot replace that result.
How updates should be published.
Future status updates should identify their date, tested version and scope. Live endpoint health, operator incidents and development milestones should be distinct feeds.
The public site does not automatically change this statement when a server returns a response.