Right now, all AVS operators write their individual data to the chain, which then are aggregated by the verifier contract once a given threshold is met. This is not always the ideal approach.
We should document and architecture out another approach using off-chain aggregation:
- Each Operator should sign a message (not a tx), which is sent to an aggegrator (not the chain)
- The aggregator awaits some time-limit or until threshold is reached.
- Aggregator submit all operator results to the verifier contract and triggers task resolution (aggregator address should not be permissioned, each signed operator response will be compared to their key)
- Update the verifier contract (all verifier contracts) to accept either format ideally, and then call into same logic to verify.
Aggregator can be centralized to start (as long as you can swap who runs it easily). Consider what would be a decentralized version, but no need to go too far down that rabbit hole.
Right now, all AVS operators write their individual data to the chain, which then are aggregated by the verifier contract once a given threshold is met. This is not always the ideal approach.
We should document and architecture out another approach using off-chain aggregation:
Aggregator can be centralized to start (as long as you can swap who runs it easily). Consider what would be a decentralized version, but no need to go too far down that rabbit hole.