🛠️ What if Kleros rulings were published in the @eas_eth attestation format so any contract or backend could check a single, machine-readable record? Check @AminCad post about this idea. What do you think?
AminCad Ξ🐬🔊 - evm/acc
AminCad Ξ🐬🔊 - evm/acc15.8. klo 19.58
The Ethereum Attestation Service (EAS) (@eas_eth) has become the universal, permissionless registry for structured claims. What’s missing is a standardized layer between EAS and the specialized verification engines we already have, such as Kleros for decentralized arbitration, UMA’s Optimistic Oracle, zero-knowledge proof verifiers, etc. I’m proposing that the community explore a new EIP for a Verifiable Attestation Protocol built around two core concepts: AttestationRouter – A standardized onchain contract (could be implemented as an EAS Resolver) that can aggregate and route attestations from multiple sources. The router’s logic would be driven by a machine-readable verificationSpec provided with each task. Modular Verification Handlers – A common interface for pluggable verification modules, whether human-driven (Kleros, UMA), cryptographic (ZK proof verifiers), or data-driven (IoT oracle feeds). EAS already provides the universal ledger. Kleros, UMA, ZK verifiers, and DONs are mature enough to serve as verification modules. A standardized AttestationRouter + handler interface would connect these pieces into a coherent "truth layer" for both objective and subjective verification.
9,84K