Consensus-verifiable obligations for real-world deliverables.
ProofSpec is a reusable GenLayer Intelligent Contract primitive for determining whether an agreed specification has been satisfied by verifiable evidence.
A contract should not ask AI whether something is "good."
It should ask whether an explicit specification has been satisfied by verifiable evidence.
ProofSpec follows four principles:
- Spec-first, not prompt-first
- Evidence over opinion
- Unverifiable is not failure
- Semantic equivalence, not identical prose
- PASS
- PARTIAL
- FAIL
- UNVERIFIABLE
- AI agent agreements
- Freelance deliverables
- DAO grant milestones
- Hackathon bounties
- Service-level agreements
- Bug bounty verification
ProofSpec V2 — live on GenLayer Studio with validated consensus behavior.
ProofSpec V2 is deployed and running on GenLayer Studio.
Contract: 0x1423CaEFCB857942C3b0cD63D2CA745D2cB93AEc
Studio: https://studio.genlayer.com/?import-contract=0x1423CaEFCB857942C3b0cD63D2CA745D2cB93AEc
- Status: FINALIZED
- Verdict: PASS
- Score: 100
- Reason: SPEC_SATISFIED
The submitted webpage was successfully fetched and verified as publicly reachable with visible content.
- Status: FINALIZED
- Verdict: UNVERIFIABLE
- Score: 0
- Mandatory failed: 0
- Mandatory unverifiable: 1
- Reason: MANDATORY_EVIDENCE_UNVERIFIABLE
The evidence could not be fetched. ProofSpec correctly treated missing evidence as unverifiable rather than failed.
The website itself was verifiable, but its prerequisite manifest was unavailable.
- Status: FINALIZED
- Verdict: UNVERIFIABLE
- Score: 0
- Mandatory failed: 0
- Mandatory unverifiable: 1
- Reason: MANDATORY_EVIDENCE_UNVERIFIABLE
This demonstrates deterministic dependency blocking: a downstream obligation cannot receive credit when its prerequisite is not satisfied.
Validators handle evidence interpretation and obligation classification.
The contract deterministically derives dependency blocking, weighted score, mandatory gates, and final verdict.