How Veral works.
Veral reads every public source the engine can reach about a subject, computes a deterministic score on a published formula, and signs the answer on Ethereum. The worked example below is an AI-Agent reading — Veral's flagship cert.
Every public source the engine can reach.
For each subject Veral fetches the public evidence in parallel — source-verification registries, on-chain history, ENS records, EAS attestations, audit registries, identity stamps, social graph, security signals. Every fetch is cached with a published TTL and carries provenance so any reader can re-fetch the same evidence and reach the same conclusion.
On the worked example below, the engine reaches usable evidence across most of its wired AI-Agent-profile sources. Each line is one extractor and the finding it produced.
- Safe multisig · 2-of-3 Safe controlling the agent address
- Upgradeability · non-proxy contract, no admin-key escape hatch
- EAS attestations · three attestations on file, two from trusted issuers
- ENS · multi-month-old ENS name with two published subnames
- ENS records · five populated text records — discovery, links, descriptors
- Ethereum mainnet · live contract deployed, sustained transfer activity
- L2 deployments · verified deployment matched on one L2
- Counterparty graph · 14 unique counterparties over 90d, no wash pattern, no sanctioned address
- GitHub · public repo with tests, CI, license, releases shipped in the last year
- Gitcoin Passport · self-asserted passport with 12 stamps
- Farcaster · Farcaster ID with two verified address bindings
- POAP · 8 unique event POAPs, most recent earlier this year
- Sourcify · two contracts verified end-to-end
- Etherscan · every controlled contract source-verified
A deterministic formula, no AI, no opinions.
The aggregator combines the evidence into a per-macro score, weighted by the methodology's locked weight vector, then rolls up to a single 0–100 number. Same evidence in, same score out, on any device, at any time. Every macro carries its full weight at all times: a macro with no signal (here M4 Financial and M7 Transparency) contributes zero points and is never re-normalized away — that forfeited ceiling is how breadth of coverage becomes part of the score.
The Points column is each macro's base contribution (weight × score); the five carried macros sum to 43.9. A bounded corroboration lift — capped extra credit when independent sources agree — then brings the base to the 46 / 100 headline. The lift can never exceed its cap, so the score stays reproducible from the published evidence bundle.
These numbers are computed from Veral's pinned calibration snapshot — the locked reference the engine's regression tests enforce, so this example never silently drifts. The subject's live reading grows as it publishes new evidence: see freysa.eth's current reading.
Every certificate reads back as a 0–100 number on the same evidence-bound scale.
- 0 – 19 · Adverse
- 20 – 39 · Caution
- 40 – 59 · Limited
- 60 – 74 · Established
- 75 – 89 · Strong
- 90 – 100 · Exemplary
Signed and published on Ethereum.
The reading is published as an EAS attestation anchored to the subject's ENS namehash. The on-chain certificate is verifiable by any reader who recomputes the score against the published evidence bundle, and shareable as a verification URL that is fixedfor the life of the attestation on the issuing chain — currently Base.
- Schema
- EAS · Veral Cert schema v2
- Network
- Base (pinned worked-example snapshot)
- Subject namehash
- 0x6e6cb1c7…687b95c
- Operator
- veral.eth (verified against operator key)
- Anchored to
- subject ENS namehash
- Verification URL
- /cert/<UID>
See it live. Get yours.
- See it live at /b/freysa.eth
Free per-subject diagnostic. The breakdown shows every source the engine reached for the subject and what each one contributed.
- Get yours at /cert/new
Request a Public certificate. The reading is signed and published as an EAS attestation; the verification URL is fixed for the life of the attestation on theissuing chain — currently Base.