0x6F74…90E850 gates5 circuitsLAW helps vault developers inspect policy decisions against real circuits on X Layer. Choose a withdrawal scenario, compare the expected result with the deployed processor, and export the evidence.
Built and deployed on X Layer using real OKB. Courtroom balances and withdrawals are simulated; trying them needs no wallet. The reference vault is not deployed or audited.
5 circuits on X Layer.
One inspectable policy toolkit.
00ALLOW01ALLOW10ALLOW11DENYFive building blocks for explicit policy decisions. Start with SpendLimit, explore approval and mode inputs, then see RuleMux combine two rules.
Two connected ideas, separate demonstrations. These cards evaluate circuit inputs on X Layer when you request verification. The Courtroom separately simulates a daily-limit adapter using SpendLimit logic; it does not apply all five circuits to withdrawals.
Are both restriction flags active?
Two flags. Deny only when both are high.
deny = ah AND dh0x00Are at least two approval inputs present?
Approval inputs, not collected wallet signatures.
pass = approvals ≥ 20x05How does the selected mode change the decision?
FOMO allows. FEAR and HOLD share the AND guard. EXIT denies.
deny = exit OR (nonFomo AND ah AND dh)0x04What happens when the liveness input is off?
The circuit reads a liveness bit. It does not measure time.
deny = NOT alive OR (ah AND dh)0x01How do spend and quorum rules combine?
Both the spend restriction and approval count matter.
deny = (ah AND dh) OR NOT quorum0x14These controls represent circuit inputs. They are not authenticated signatures or an on-chain heartbeat timer. They do not change the separate Courtroom budget.
A policy-verification workspace. Model a fixed 0.10 OKB daily allowance, then compare the derived input with the deployed circuit.
Start with 1.00 OKB and a 0.10 OKB allowance. Starting or replaying resets the demo; manual actions leave the walkthrough.
Follow the sequence or enter a custom amount below. Compare each result on X Layer in the decision log.
Active policy: SpendLimit · circuit 1. The adapter derives [overLimit, 1]. Mood, Quorum, Dead Man and RuleMux are not applied to Courtroom withdrawals. UTC-day resets affect the current allowance, not captured request history.
Evaluation updates scenario balances locally. In the decision log, optionally compare a request’s captured input with SpendLimit on X Layer. RPC results never move funds or change the simulation.
Choose an amount and evaluate it.
Then compare the captured input on X Layer.
Export the result for your integration review.
dailyLimit: 0.1
// does the circuit agree?A rule and an expected result are not evidence that the deployed circuit behaves the same way.
spent + requested > limit
→ packed input → real eval()Compare expected and actual output at a recorded block, then export the evidence. Balances stay simulated.
overLimit = spentToday + requestedAmount > dailyLimitThe reference vault derives this predicate from its own state. It sends [overLimit, 1] to the pinned AND circuit: 0x02 → ALLOW, 0x03 → DENY. It also independently enforces the numeric limit. The new vault contract is reference code, not a deployment claimed by this UI.
Deployed processor. Recorded evidence. Open source. No wallet required.
7 listed transaction receipts checked at block 72,566,407 on 7 October 2026. A historical snapshot, not a live status or security audit.
A local test result, an RPC response, and a transaction receipt prove different things.
68 / 68 evaluations and 7 listed receipts verified at block 72,566,407. This is a recorded snapshot, not continuous monitoring. Read the verification snapshot ↗
Addresses are taken from the project manifest. Use the read-only verifier to check chain ID, factory registration, receipts, issuance parameters, and all 68 circuit cases at a recorded block.
Inspect processor ↗Reproducible checks cover encoded netlists, demo decisions, and reference-contract behavior on an isolated local EVM. These are not a security audit or evidence of a deployed vault.
npm ci
npm test
npm run verify:mainnetVerification guide ↗Source code and verification instructions are published in the repository.
This release does not offer bond escrow, automatic slashing, author revenue sharing, authenticated multisig approvals, token-launch buttons, or an optimisation bounty market.
Registry administration and upstream processor upgrades remain trust boundaries. A stored netlist hash alone cannot prove unchanged execution.
Threat model & limitations ↗Fees are additional. Transistors are used to tape out new circuits; reusing an existing circuit does not require a new mint. Demand depends on builders choosing to create useful circuits, not a promise of yield or price appreciation.