THE REAL STATE · WITHOUT GLOSS

What holds, what does not hold yet

This is this site's credibility contract: the project is in development, and every page carries the status of what it describes. Here is the overall state — nothing is flattered.

For developers Back to home

The detailed audit — with file-by-file evidence — is kept current in the project repository (docs/state-of-the-system.md).

DEVNET 43911 — THE HEARTBEAT, LIVE

Measuring the chain…

Real numbers read from explorer.aletheia-chain.com — not a simulation.

01 — Four domains, four verdicts

What is solid, what is still fragile

Load · Storage · Security · Durability: for each, what holds and what remains. Recent fixes (signatures, proof of possession, RPC limits) are taken into account.

Load

Browser mining is lightweight — a bounded CPU budget, explicit consent, proof-of-work re-verified by the server (a fake nonce is refused).
AI reply costs still need bounding — the operator's keys fund the replies; the limit is an open work item, listed in the audit.

Storage

The chain replays deterministically — history re-verifies identically (tens of thousands of blocks).
Storage is not bounded yet — growth is assumed today; the limit is to be built.

Security

The chain is re-verified — blocks, finality, roots; model weights never reach the server (structurally tested).
August's critical flaws are fixed — signatures on debits, proof of possession on wallet links.
The audit continues — every new surface is put through the same sieve before being announced.

Durability

Deterministic replay holds — the canonical history rebuilds identically after restart.
Visitor backup is an acknowledged gap — a wallet key that never leaves the browser (a security choice) cannot be recovered elsewhere; loss is loss, until the export to be built.

02 — How this state is verified

Evidence, not impressions

This site does not describe what the project wishes it were — it describes what is verified.

How: Crossed audits: the code graph to locate, then direct file reading. Every claim has a file:line anchor.
When: At every code change: the repository rule requires updating the evidence, not just the text.
What it does not say: No dates, no promises. Open work items are listed — being open is their nature.

A stated limit is not a shame: it is a visible work item. This page is what makes the rest of the discourse credible — it is linked from the home and will stay so.