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
  • Framework Architecture
  • Execution Service and Validation Service
  1. AVS Framework

Abstract

PreviousUse CasesNextQuick Start

Last updated 19 days ago

AVS is:

  • Complex system designed for a unique computing purpose.

  • Decentralized system that runs its own validator set.

  • Proof of Stake (PoS) network.

The AVS protocol requires an infrastructure to execute off-chain computational tasks, reach on-chain agreements on arbitrary tasks, submit and audit the Operators' work, deploy customized business logic, propagate internal and cross-chain messaging, configure governance rules, define registration policies, and distribute rewards and penalties based on attestations.

The Othentic Stack allows developers to self-deploy (1) customized off-chain execution and (2) a network of Operators that run and verify arbitrary tasks.

Framework Architecture

The Othentic Stack is designed to balance cost-efficiency, security, and high throughput by leveraging both L1 and L2 layers.

  • L1: The governance layer is deployed on L1 to ensure the highest level of security, integrate with the shared security protocol contracts, and manage critical governance operations.

This design ensures a scalable and efficient AVS while optimizing for cost and performance.


Execution Service and Validation Service

AVS teams are required to develop two services: the Execution Service and the Validation Service, which can be implemented in any programming language.

L2: The task verification layer is deployed on L2 to minimize operational costs while maintaining availability, high throughput, and low latency. L2s provide a faster and cost-effective environment for handling task submissions and attestations. A single AVS can operate across networks.

executes the and generates a . Once the task is successfully completed, the node publishes the results via peer-to-peer networking for to discover.

validate a task via a quorum that votes on the validity of the executed task; each task must be attested as either "valid" or "invalid". The scheme allows the execution and validation of any type of service, providing a foundation for a wide range of applications.

multiple L2
Execution service
Validation service
Proof of Task
task
Performer node
Attesters nodes
Attesters nodes