Economic assurance for AI-agent claims
Trust, backed by consensus.
SureLayer lets an agent or operator put real GEN behind a precise claim. When challenged, GenLayer independently evaluates the evidence and settles the warranty.
ASSURED
A claim becomes more useful when someone is willing to lose money if it is wrong.
01 / The premise
Specific claims deserve specific consequences.
AI output is cheap to produce and difficult to audit. SureLayer turns a bounded assertion into an observable economic commitment.
Issue
Define the claim, warranty criteria, artifact, and bounded evidence. Lock a GEN bond.
Challenge
A second participant posts a challenge bond and identifies the criterion they contest.
Resolve
GenLayer consensus evaluates untrusted sources and records a structured verdict.
02 / The ledger
Outcome follows the evidence.
Funds move according to a small, explicit state machine. There is no administrator who can rewrite a verdict.
03 / Why GenLayer
Not a backend boolean.
A centralized service can ask an LLM for a verdict. It cannot give every validator an opportunity to independently inspect the evidence and converge on the economic decision.
- 01Independent evaluationLeader output is checked against validator-derived verdict, evidence state, criteria result, and support count.
- 02Untrusted sources stay untrustedWeb text is bounded, marked as data, scanned for prompt injection, and never treated as protocol instructions.
- 03Final state, not optimistic UIThe application reads the latest finalized contract state and distinguishes submission from a decided outcome.
04 / Security model
Small enough to audit. Serious enough to settle.
The contract keeps the trust boundary narrow: bounded data, explicit transitions, pull-based credits, and no privileged verdict override.
Finite by design
Statements, criteria, URLs, source count, evidence extraction, pages, and consensus work all have explicit limits.
Liabilities are visible
Locked bonds and withdrawable credits are tracked on-chain and checked against the contract’s expected assets.
Timeout is permissionless
If a challenged resolution cannot finish, either participant can recover their own bond after the deadline.
05 / Developer path
Integrate around a final contract state.
SureLayer exposes a compact contract interface. The server normalizes reads; the connected wallet signs writes; the contract remains the source of truth.
Write a warranty
Call the payable create method with a claim, criteria, artifact reference, and bounded source list. The bond is real GEN, not a UI balance.
create_claim(statement, artifact, hash, criteria, sources)Read and challenge
Read finalized pages and detail projections, then let a challenger post an exact bond against a concrete criterion.
get_claim(id) → state, evidence, timeline06 / Roadmap
Protocol before polish. Evidence before expansion.
Only shipped behavior is presented as live. Planned work remains explicitly labeled.
Core assurance loop
Bonded claims, one active challenge, independent evidence evaluation, three verdicts, pull credits, and timeout recovery.
Operational tooling
More detailed finality and fee inspection, richer developer helpers, and stronger evidence extraction once the network contract is stable.
Composable warranties
Delegated claim templates and additional artifact adapters only after the core economic invariants have production evidence.
07 / FAQ
Questions worth asking before money moves.
Why not use a regular EVM contract?
A regular contract can enforce bonds and transitions, but it cannot natively perform the semantic evidence adjudication that SureLayer asks validators to independently evaluate.
What if sources disagree or disappear?
The evaluator records the evidence condition and returns INCONCLUSIVE when reliable binary support cannot be established. A timeout remains available if consensus cannot complete.
Can an issuer or administrator override a verdict?
No. There is no admin verdict function. Resolution is permissionless while the challenged claim is within its resolution window.
When is a transaction actually final?
After GenLayer’s final transaction status and successful contract execution are observed. A submitted wallet transaction is only progress, not a settled warranty.
08 / Protocol status
Use the chain as the source of truth.
There are no invented activity numbers here. If a deployment is not configured or readable, SureLayer says so and leaves the live view empty.