Othentic
  • Introduction
    • Introducing Othentic Stack
    • Use Cases
  • AVS Framework
    • Abstract
    • Quick Start
    • Othentic CLI
      • Key Management
      • Contracts Deployment
      • Operator Registration
      • AVS Logic Implementation
      • Operator Deposit
      • Node Operators
      • Rewards Distribution
      • P2P Config
        • Custom P2P Messaging
        • P2P Auth Layer
        • Metrics and Monitoring
        • Logging
        • Persistent storage
        • Latency
      • CLI Command Reference
    • Smart Contracts
      • AVS Governance
      • Attestation Center
      • Hooks
        • Task Logic
        • Operator Management
        • Rewards Fee Calculator
      • OBLS
      • Othentic Registry
      • Message Handlers
    • Othentic Consensus
      • Abstract
      • Task & Task Definitions
      • Leader Election
      • Proof of Task
      • Execution Service
      • Validation Service
      • Voting Power
      • Rewards and Penalties
      • Internal Tasks
    • FAQ
    • Supported Networks
    • Explainers
      • Networking
      • Multichain
      • Production Guidelines
      • Operator Allowlisting
      • Governance Multisig
  • External
    • AVS Examples
  • GitHub
  • Othentic Hub
Powered by GitBook
On this page
  • Structure
  • Task Execution
  • Task Validation
  1. AVS Framework
  2. Othentic CLI

AVS Logic Implementation

Every AVS must implement both execution and validation logic.

PreviousOperator RegistrationNextOperator Deposit

Last updated 3 days ago

We recommend to use the repository as a boilerplate for your AVS. It provides an example implementation that helps clarify how the network functions and allows you to get up and running.

Structure


The AVS logic implementation consists of two main components:

Each component runs as a separate service: handles execution, while is responsible for validation.

Task Execution

The Task Performer must create a , which can be validated by Attester Nodes. This proof could be the result of a calculation, a ZK proof, the CID of a JSON on IPFS, etc. Task Validation implementation should be able to use this proof to attest to the task properly.

In order to publish the task, the Task Performer must send a JSON-RPC request to an arbitrary node on the network, which propagates to its peers. See the function in the Task_Performer module to learn how to send such requests.

Task Validation

Attester nodes are responsible for running the Validation Service, which contains the task validation logic. This is similar to how the Consensus Client communicates with the Execution Client in Ethereum.

The Validation Service must implement the /task/validate endpoint.

When an Attester receives a proof of task from the Performer, it uses the Validation Service API endpoint to verify the task.

AVS Examples
Execution Service
Validation Service
Execution_Service
Validation_Service
proofOfTask
sendTask