Ops console

Run a demo scenario and watch the four verifiers work, vote by vote, through to the contract decision and payments.

Open the large screen view

S1Delivered

Genuine report

Verified, funded and delivered. Simulated NGOs bid; the proof checks out.

S2Rejected

Keyword attack

Reports repeat "flood" with no outside evidence, and one hides an instruction to the verifiers.

S3Rejected

Flood of fakes

Many reports from one sender in a few minutes.

S5Payment withheld

Inflated proof

The delivery claim doesn't add up: far more households than the plan.

Run sends the scenario's reports through the agent runner: four verifiers vote, the contract decides, simulated NGOs bid and deliver. Every step is a testnet transaction.

Run

S1 · Genuine report

Step 14 of 14

CCase submittedS1 · Genuine report · s6177-2024-09-10-003-s1
GGeo votedReasoning not in evidence storage. 91% confident.Yes
FFact votedReasoning not in evidence storage. 94% confident.Yes
SSeverity votedReasoning not in evidence storage. 92% confident.Yes
RRed team votedReasoning not in evidence storage. 89% confident.Yes
§Contract decision: FundedFunded with 4 yes votes. Cap 5,000.00 USDC: the lowest of the tier limit, 20% of the pool and the daily limit left.
→Bid · ngo-ra…tnet6 hours4,600.00 USDC
→Bid · ngo-ba…tnet14 hours4,000.00 USDC
→Bid · ngo-fr…tnet18 hours3,400.00 USDC
→Awarded to ngo-fr…tnetFirst payment, 40%1,360.00 USDC
→Proof of deliverySubmitted
→Delivery checks out4 of 4 verifiers agree · needs 2
→Second paymentCase delivered2,040.00 USDC

Contract

Funded

cap 5,000 USDC

Funds at 3 yes. Rejects at 2 no. Anything else goes to a coordinator.

Waiting for a coordinator

Cases where neither rule was met.

No cases are waiting for a coordinator.

Only an account registered as a coordinator on the relief contract can confirm or reject; anyone else gets the contract's refusal. Each decision is its own transaction.