Abstract

Protocol core service can be broken down into units called “Tasks”. Each Task represents a unit of work to be carried out by the Operators.

Othentic Consensus is a scheme to execute, validate, and approve any given task. Powered by a modular consensus engine, the Othentic Consensus allows the execution and validation of any computational use case.

In the peer-to-peer consensus process, Operators perform several roles – Performer, Attester, and Aggregator. Performers execute the off-chain computations, whereas Attesters make claims about the execution and cast their attestation using BLS. These claims are cryptographically signed to ensure the authenticity and immutability of task execution. The weight of their attestation is proportional to the amount of (re)stake assets locked to secure the network, and determine the influence of individual Attester over the consensus process. Aggregators collect the attestations, calculate the voting power of individual Attester, aggregate the signatures into one BLS signature, and submit the execution results on-chain.

Task Performer

Task Performer is an AVS Operator that executes a task. Task execution is handled by the Execution Service, which runs as a Docker container and can be implemented in any programming language.

Execution Service generates a Proof of Task, and publishes the results to peer-to-peer network for Attester nodes to discover.

The RPC call that the Task Performer sends to the p2p network:

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

Task Attesters

Task Attesters are AVS Operators 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 Validation Service.

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

Task 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.