Transparency
WHAT IS ACTUALLY LIVE.
Most of this ecosystem is not shipped yet. ASHER is not deployed, no Genesis round is open, and Autopilot and Copilot are still beta. Here is the list, in four words — live, beta, in development, planned — with nothing rounded up.
Status
Live, beta, in development, planned
Four words, used strictly. LIVE means shipped and available. BETA means available and labelled as beta. IN DEVELOPMENT means being built, with no production deployment. PLANNED means it does not exist yet.
| Component | Status | What that means today |
|---|---|---|
| ExecutionTerminal tier | LIVE | Shipped and available. Non-custodial: funds stay in your own account, and the session key that signs orders cannot withdraw. |
| ExecutionCopilot tier | BETA | Available, and beta. Non-custodial on the same terms as Terminal: no deposit, no managed account, and a session key that cannot withdraw. |
| ExecutionAutopilot tier | BETA | Available, and beta. Non-custodial on the same terms as Terminal: no deposit, no managed account, and a session key that cannot withdraw. |
| AsherLabsNewer application build | IN DEVELOPMENT | No production deployment exists. The only host serving it is a quality-assurance host, which is not published. |
| ASHERToken contract | PLANNED | Not deployed. No production contract has been supplied, audited or deployed, and no address is published. |
| ASHERWallet integration | PLANNED | Not deployed. There is no wallet library in the runtime dependency set of this site. |
| ASHERStaking | PLANNED | Not deployed. Nothing can be staked, because there is nothing deployed to stake. |
| ASHERTreasury | PLANNED | Not deployed. There is no treasury contract and no treasury balance to report. |
| ASHERGovernance | PLANNED | Not deployed. There is no governance mechanism of any kind — no governance contract, and nothing to vote with. |
| ASHERPoints ledger | PLANNED | Not deployed. No points are being accrued or recorded anywhere. |
| GenesisContribution round | PLANNED | No round is open. Contributions are disabled in code, and minimum and maximum contributions have not been set. |
| GenesisVesting schedule | PLANNED | 10% at TGE and 90% over 24 months is a working parameter, not a final term. No token generation event is scheduled. |
Measurement
What we do not measure, and why we show nothing instead of a zero
A blank is honest. A zero is a claim. Where no instrument exists, this product shows nothing — in its own internal console as well as on this page.
- Latency
- There is no latency measurement in this system, so there is no latency figure to publish. A figure produced for a page rather than by an instrument would be a guess with a decimal point on it.
- Error rate
- There is no error-rate measurement either. Nothing aggregates failures into a rate, so no rate is shown.
- What the admin console does about it
- Several metrics in our own internal console read NOT AVAILABLE, because no honest source for them exists. They read NOT AVAILABLE rather than 0, because a zero is a measurement — it claims somebody looked and found none — and nobody looked. The people running this see the same blanks you do.
- Uptime, users, audits, compliance
- No uptime figure, user or customer count, third-party audit, security certification, compliance standard or regulatory status appears on this page. None has been verified. Each is the kind of claim that is cheap to write and expensive to retract, so it is not written.
Genesis
The current state of Genesis
Nothing is open, nothing is deployed, and the parameters that exist are working values rather than final terms.
- The round
- No Genesis round is open. Minimum and maximum contributions have not been set, so there is no size to quote.
- The contract
- No production contract has been supplied, audited or deployed, and no address is published. There has been no contract audit, because there is nothing yet to audit.
- Why it cannot open by accident
- Opening a contribution requires production status, an explicit live flag and well-formed, non-zero contract addresses — all three at once. A flag flipped on its own cannot open a sale, a placeholder like "TBD" does not pass address validation, and the zero address is rejected.
- Vesting
- 10% at TGE and 90% over 24 months is a working parameter, not a final term. No token generation event is scheduled, so the schedule has no start date to hang off.
- The arithmetic
- Allocations are computed in integer arithmetic from each round’s cap ratio, never from a rounded decimal price, so a fully subscribed round lands exactly on its cap. This is asserted by tests rather than checked by eye.
Verify it yourself
Where you do not have to take our word
Some of the claims on this site are checkable from your own browser in under a minute. Those are listed here. The rest are stated as what they are — our account of our own system — and this page tries hard not to blur the two.
- The security headers
- Open your browser’s network panel and look at the response headers for this page. The Content-Security-Policy, X-Frame-Options, HSTS, Referrer-Policy, Permissions-Policy and nosniff headers are served on every route, from one place in next.config.mjs.
- That no third-party code runs
- In the same panel, look at what the page requests. Every request goes to this origin. There is no CDN, no analytics, no tag manager, no external script and no external font — so you can confirm the claim yourself rather than take it.
- That no contract exists
- There is no address to paste into a block explorer, and that absence is the verification. When a contract is deployed, the address will be published and you will be able to check it on-chain instead of reading about it here.
- The screenshots on this site
- They are real product screenshots, not mock-ups, cropped to exclude account balances and avatars. Provenance for each one is recorded internally — where it came from and what it shows.
Keep reading
What protects you
The companion to this page covers custody, the Genesis safeguards, data minimisation, record integrity and this site’s own security posture.