Ungate InfiniRoute AVS
  • 🔥Introduction
    • Overview
    • Scope
  • 📓ARCHITECTURE
    • Abstract
    • Keys Components
  • 🧠Inference Engine
    • Abstract
    • User Interface Layer
    • Coordination Layer
    • Data Layer
  • ⚓AVS
    • Abstract
    • Task Consensus
    • Consensus Engine
    • Rewards and Penalties
  • 🏪Models Marketplace
    • Abstract
    • Externally Hosted Models
    • Benchmarking Engine
    • Marketplace Economy
  • 👩‍💼Operators
    • MainNet
      • Registration
      • Installation
      • Quickstart
    • TestNet
      • Installation
      • Registration
      • Quickstart
  • 🎁Summary
    • Immediate Next Steps
    • Building the First SubNet
    • Future Vision
    • Conclusion
Powered by GitBook
On this page
  1. AVS

Task Consensus

PreviousAbstractNextConsensus Engine

Last updated 10 months ago

Task Consensus is a scheme to execute, validate, and approve any given task. We will be using Othentic Stack to deploy our AVS infrastructure. Powered by a modular consensus engine, the Othentic Task Consensus allows the execution and validation of any computation use case. It is cryptoeconomically secured and uses stake-weighted power.

The consensus algorithm leverages the leader election mechanism, a process for entities (Task Attesters) to make claims about another entity (Task Performer). These claims are cryptographically signed to ensure the authenticity and immutability of task execution.

Performer

Task Performer is an AVS Operator that executes a task, provides a Proof of Task, and sends the results to Attesters. After successfully executing a task, the Task Performer publishes an event via peer-to-peer networking for Attester nodes to discover.

The RPC call that the Task Performer sends to the Attestor Nodes:

{
    "jsonrpc": "2.0",
    "method": "sendTask",
    "params": [<proofOfTask>, <data>, <taskDefinitionId>,  <performerAddress>, <signature>]
}

Attesters

Task Attesters are AVS Operators' quorum that attests to the validity of the executed task. Each task must be attested as either "valid" or "invalid".

The Operator's voting power is proportional and calculated against the amount of re-stake assets staked on the shared security layer, referred to as “dynamic voting power.” The re-staked effective balance determines each Operator's influence in the consensus process. If over ⅔ of the quorum's voting power attest "valid", the task is considered approved. If over ⅓ of the quorum's voting power attest "invalid", the task is rejected, and the quorum executes a slashing event to the Performer. The Attesters run the validation logic using a local HTTP request to the AVS WebAPI.

curl -X POST \
  http://localhost/validate_task \
  -H 'Content-Type: application/json' \
  -d '{
    "proofOfTask": "your_proof_of_task_data",
    "taskDefinitionID": "your_task_definition_id"
  }'

Aggregator

The Aggregator listens to events from the Attester nodes and monitors the necessary voting power contribution to a certain task. The Aggregator aggregates the signatures of the Attesters into a BLS aggregated signature and submits a transaction to the AttestationCenter smart contract. After successful validation, the Performer, Attesters, and Aggregator are eligible to claim task rewards.

⚓
Task Consensus Flow Diagram