Architecture and trust boundaries
Every result can be traced from public input to reward.
Measurement happens offchain because every failure case must be computed efficiently. Commitments and rewards belong on Ethereum because no sponsor should be able to rewrite the final result after seeing who won.
The complete evidence path
- 01Challenge manifest
Dataset, constraints, metric directions, and lifecycle are published.
manifestHash - 02Builder solution
A human or agent submits allocation values against one context.
contextHash - 03Deterministic evaluator
Correctness, every independent axis, and Frontier contribution are recalculated.
resultHash - 04Reward allocation
Exclusive contribution converts a fixed pool into participant amounts.
allocationRoot - 05Ethereum settlement
The pool commits once; each address can receive or claim once.
transactionHash
Hash relationship
Change an input; change the evidence.
Settlement invariants
The contract limits what any operator can change.
- A challenge allocation can be committed only once.
- The committed reward total cannot exceed the funded pool balance.
- A recipient cannot receive the same challenge reward twice.
- If batch distribution skips an address, that address retains an individual claim path.
Ethereum settlement evidence
Demo reward allocation recorded on Sepolia.
Ethereum fixes the challenge commitment and final allocation, prevents a second commit or double claim, and lets anyone verify who received the reward.
- Status
- Recorded on Sepolia
- Reward pool
- 0x6866fd…80c5ae
- Demo token
- 0xb6f042…1592e1
- Final result root
- 0xfe1b4b…0706dd
- Allocation commitment
- 0x96fd7a…839f2c
- RewardPaid tx / block
- 0xd976a9…9ad708 · #11652735
- Recipient balance
- 0 FDT → 10000 FDT · +10000 FDT
- Scope
- Sepolia demonstration payout to the deployer wallet—not a completed public tournament.
This step only connects a wallet. It does not request a raw message signature, token approval, or transaction.
Verify in source