Consensus for facts that APIs can't answer.
Turn a real-world fact specification into a canonical, inspectable on-chain verdict — with evidence policy, provenance, freshness, and history attached.
Facts APIs can't answer
A price feed can tell you what happened to a number. It cannot, by itself, establish whether a product shipped, a grant cleared a milestone, or a policy changed.
Did the product ship?
Semantic claims need context, sources, and a rule for deciding.
Was the milestone met?
Evidence can be real without being independent. Provenance matters.
Is the service operational?
A current answer needs a freshness regime, not a confidence badge.
Did the rule change?
Publish a fact specification and let consensus make the verdict durable.
From a question to a record
Evidra turns a precise fact specification into a resolved, inspectable state transition.
Define the subject, predicate, value, time, and policy.
Supply bounded HTTPS sources with evidence provenance.
GenLayer validators evaluate the rule against isolated evidence.
Canonical and latest resolutions remain separately queryable on-chain.
Sources are not votes
Evidra records source class, origin, provenance group, independence, and policy eligibility. A copied article across three domains is still one lineage.
Classify
Official, primary, independent secondary, community, derived, and unknown are explicit protocol values.
Group
Provenance groups stop derivative copies from inflating the independent-source count.
Fail closed
Policy requirements can produce an unresolved result instead of an invented boolean.
Read the record, not the headline
Every public Fact page separates the canonical resolution from the latest attempt and shows where the projection was read.
Studio Dev
Current public data is read from the Phase 1 API projection and can be checked against finalized chain reads on a Fact page.
- Chain 61997
- Resolver status unavailable
- — indexed facts
Give agents a fact they can verify.
Use the read API for projections, the frozen protocol client for finalized reads, and a browser wallet for user-originated writes.
Developer entry pointif (fact.canonical_resolution?.outcome === 'TRUE') {
return fact.freshness;
}