PolyAVS is an oracle specifically designed for prediction markets. It leverages the shared security of AVS, providing a transparent and censorship-resistant mechanism to ensure the accuracy of each event. To maintain sufficient decentralization, PolyAVS offers a dispute mechanism, allowing those with concerns about the results to challenge them. Operators who provide incorrect results will have a certain amount of tokens confiscated.
Here is the complete process from request to settlement of the event (without dispute).or
In the above diagram, except for the operator who needs to register in Eigenlayer in advance, the Requestor / Proposer / Settler could be anyone.
If anyone is not agreed with the operator’s verification result, he can request a dispute for re-verification of the result and the stake assets will serve as collateral. The steps in the diagram continue from the previous diagram.
There will be two possible outcomes here
- If disputer is wrong, then the disputer's staked assets will be confiscated.
- If operators is wrong, then the assets delegated to operator will be confiscated
- Holesky
- OracleCore: 0x86968D4987a0FEed1F6e8CfF560AFcA755A931cB
- ECDSAStakeRegistry: 0xc7a3659e894c95d70f9a8ec95127e56c12032878
- Check current path in contracts
cd contracts- Build contracts
forge build- Test contracts
forge test-
Check current path in project root
-
Install dependencies
pnpm install- Run operator to monitor event
ts-node ./operator/main.ts