··· Enter EVO

HELP & SUPPORT

Honest answers
for the beta.

EVO is in an invited closed beta on Kaspa testnet-10. This page is the honest version of support: what to try first, what's expected, and how to reach a human.

TRY THIS FIRST

When something looks wrong

The page won't load or is stuck

Check /api/health — it reports the running build and status. A hard refresh (Ctrl+Shift+R) clears stale client state. Your EVO's life is stored server-side and survives reloads.

A button does nothing

Look for the error text — every EVO error answers four things: what happened, whether anything was recorded, whether retrying is safe, and what to do next. Retry safety is per-operation: anything involving payment, settlement, or work orders is idempotent and safe to retry; if you only *think* a request failed (e.g. the page timed out), check whether it actually completed first — a repeated chat or state change can take effect twice.

Economic life shows EMULATOR

That's correct and labelled honestly. The default capability provider is an emulator; real settlement paths are testnet-10 only and clearly marked. Nothing in beta moves real funds.

SET EXPECTATIONS

What the beta is — and isn't

It is

An invited closed cohort. Your EVO is a persistent life with durable state, a verifiable history, and a bounded economic life on Kaspa testnet-10 — labelled as such everywhere.

It isn't

A public launch, a production mint, a wallet service, or a finished product. There is no mainnet anything in beta, and no feature that moves real money exists yet.

Your data

Your EVO's state is isolated per participant and backed up as part of the deployment. Deletion and retention boundaries are documented in the privacy draft (pending legal review).

REACH A HUMAN

Report a problem

GitHub issues — fastest

File a bug or question in the open repository. Include the error text you saw and roughly when it happened — never your invite secret, wallet keys, or any private data.

github.com/ehjohnyk/nft-evo/issues →

Security issues

Suspect a security problem? Report it privately per the security & trust page — never in a public issue.

Status

There's no public status page yet. /api/health is the honest machine-readable status for a running deployment. Scheduled maintenance is announced to cohort participants directly.