System status
A live, best-effort view of Morana testnet services, plus where the network stands on its own roadmap. Every figure here is read at request time; nothing is stored or remembered.
Node, gateway and pool status is read live from the gateway's public projection and the pool API. When that read fails no figures are shown at all — this site does not display stored or example values. Rows marked «not monitored» are not probed by this page.
Progress, counted rather than claimed
Tasks in the plan
Closed and confirmed
In progress and ahead
on the public testnet · dormant on mainnet
These four figures come from a snapshot taken up to event №2685. Anything written to the journal after that is not shown here.
These numbers are read from two generated files, not from a status meeting. The task counts come from the execution queue and say what it records as closed and open. The gate counts come from the chain source: each activation gate carries a height per network, and the figure above counts how many carry a testnet height rather than none. What a height does in practice is decided by the running network, and this page does not measure that.
What this does not say: a closed task is a task the queue accepted, not an audited feature. Nothing here is a launch date, and none is implied.
Where we are weaker than the alternatives
Our structure has no central owner, and that is true. But it describes the design, not the scale. There is no scale yet, and no table changes that.
| What is compared | Them | Us |
|---|---|---|
| External security audit | Signal and Session have passed independent reviews | not passed |
| Live users | millions (Signal, WhatsApp), a working network (Session) | zero — the network is closed, six servers of our own |
| App polish | years of work on usability | a build exists; the install-and-use experience is not finished |
| Time the network has run | years of continuous operation | there has been no public network yet |