Strict
Use when the answer is a fact. Did the flight land? What was the closing price? Validators must return byte-identical JSON. No interpretation permitted.
When code can't decide,
five AIs can.
Smart contracts move money. Intelligent Contracts decide who deserves it. Pose a subjective question, watch five LLMs deliberate as GenLayer validators, and see the Equivalence Principle deliver a verdict — live, in your browser.
Three primitives, working in sequence. The contract proposes. The jury deliberates. The principle decides. Everything else is implementation.
Python contracts that call LLMs and read live web pages. Same on-chain guarantees as Solidity, plus the ability to reason about subjective inputs no oracle can answer.
A leader executes first. A small jury of validators re-runs and votes. Disagreement triggers an appeal; appeal doubles the jury. Finality is reached when the supermajority agrees.
The rule the author writes that tells validators what "agreement" looks like. Strict equality for facts. Numeric tolerance for measurements. Rubric judgment for everything else.
The Equivalence Principle isn't one rule — it's three. Choosing the right one is the entire skill of writing an Intelligent Contract.
Use when the answer is a fact. Did the flight land? What was the closing price? Validators must return byte-identical JSON. No interpretation permitted.
Use when the answer is a measurement. How late was the delivery? What was the sentiment score? Validators must agree within a tolerance window.
Use when the answer is a judgment. Did the freelancer fulfill the contract? Is this proposal valid? Validators apply a rubric the author wrote and a sixth LLM judges agreement.
Pose a question. Pick a mode. Watch five validators deliberate. See the Equivalence Principle deliver a verdict. Disagreement triggers appeal.
"A freelancer was paid $800 to deliver a 10-slide pitch deck by Friday. They delivered an 8-slide deck on Monday. Did they fulfill the contract?"
Awaiting summons.
Awaiting summons.
Awaiting summons.
Awaiting summons.
Awaiting summons.
Each case shows the same path: the dispute, the jury's verdict, which mode fits, why Ethereum couldn't. Open one to leave with judgment, not just awe.
A split jury doesn't break the system — it escalates. Each appeal doubles the jury. Each doubling tightens the supermajority required. Disagreement has a price; agreement has a path.
Filing an appeal costs the appellant. Validators who vote with the supermajority earn fees; those who deviate lose stake. The result is a system that wantsto reach finality and punishes both lazy agreement and stubborn dissent. The court doesn't sleep, but it doesn't suffer fools either.
Take the playground further.
Read the guide, or fork it in Studio.