How Registrai publishes what it finds

Registrai shows proof, not opinions. For every project in the registry we publish the same facts: what is on chain, who controls it, how it is used, and what the project says about itself, each with the evidence behind it. We don't rate projects or flag them. You judge.

Same facts for everyone. Every project gets the same checklist, whether it has ten users or ten thousand.

Only what we can show. Every fact links to the transaction, contract or page that proves it. If we can't link it, we don't publish it.

Projects can add context. A team can add its own note next to any fact, and we publish it as written.

Security issues stay private first. If we find a leaked key or an exploitable bug, we tell the team privately and publish only once it's fixed, or after 30 days, never with the details an attacker would need.

Alerts we publish appear on the track record. See the track record.

Evidence is re-checked. Each fact and track record item shows the date its evidence was last re-checked. A daily record of what we published is stored, and its digest is written to Arc; see the record.

No personal data. We look at wallets and contracts, not people.

We correct mistakes in the open. If a fact is wrong, the correction stays visible in the project's change log. Accuracy disputes are reviewed by Registrai and one independent reviewer. Once the Milli community of verified projects is large enough, a random jury of its members will review them instead.

Nobody can pay us to change a fact. Our paid work is alerts, data access, deeper custom research and the AI visibility service, powered by Recall, whose clients we list. None of it buys coverage, silence, a directory status, a place in an index, a position in any list or different wording. See Not for sale.