Transparency

This dashboard separates configured intentions from what the deployment can currently verify. It never treats this page's build time as an on-chain verification timestamp.

Runtime verificationCopy section link

Read the status correctlyCopy section link

A successful account read establishes observed account fields at the reported slot. It does not, by itself, prove that Stayers has completed a successful launch, trade, claim or distribution.

The four feature statuses remain consistent across the portal: Live requires actual transaction evidence; Implemented means code exists; Planned means the complete feature is not implemented; Unavailable means the current integration does not support it.

Evidence boundariesCopy section link

The documentation endpoint performs read-only RPC calls. It exposes public addresses and verified measurements, never the RPC credential or private environment values.

If a configuration differs from the proposal, the dashboard shows observed fields and identifies the mismatch. If the RPC, configuration or transaction evidence is unavailable, it displays Not verified rather than fabricating a value.

No Stayers-specific audit report, verified mainnet LP lock or completed liquidity-deployment record has been established in the available implementation evidence.