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
      • Add-Ons
        • Metrics and Monitoring
        • Logging
        • Persistent storage
        • Custom P2P Messaging
    • Smart Contracts
      • AVS Governance
      • Attestation Center
      • Hooks
        • Task Logic
        • Operator Management
        • Payment Request
        • Rewards Fee Calculator
      • OBLS
      • Othentic Registry
      • Message Handlers
    • Othentic Consensus
      • Abstract
      • Task & Task Definitions
      • Proof of Task
      • Execution Service
      • Validation Service
      • Voting Power
      • Rewards and Penalties
      • Internal Tasks
    • FAQ
    • Supported Networks
    • CLI Command Reference
    • Explainers
      • Networking
      • Governance Multisig
  • External
    • Github
    • Oracle Example (JS)
    • Oracle Example (Go)
    • Oracle Example (Rust)
    • PRNG Example
Powered by GitBook
On this page
  • Overview
  • Usage
  • Types of Internal Tasks
  • Sync Voting Power
  1. AVS Framework
  2. Othentic Consensus

Internal Tasks

PreviousRewards and PenaltiesNextFAQ

Last updated 17 days ago

Overview

Internal Tasks are consensus-based tasks for internal maintenance of the AVS network.

  • Each internal task is uniquely identified and configured with a specific task definition ID.

  • These tasks are scheduled based on a specified frequency, which can vary depending on the operational requirements.

The execution of internal tasks is facilitated by the same operator set and consensus engine used by the AVS, ensuring that they adhere to the same standards of execution and validation as other AVS Tasks.

Whenever an internal task is executed, a proof of task is generated. The generated proof, along with task execution data, is broadcasted internally to the P2P network. Attesters validate the execution by verifying the proof and recalculating expected outcomes.

This robust framework allows you to concentrate on core business logic while maintaining operational efficiency in a decentralized environment.

Usage

Internal tasks are executed by Aggregator nodes when the --internal-tasks option is enabled.

Othentic-cli node aggregator --internal-tasks

Types of Internal Tasks

Sync Voting Power

A specialized internal task VotingPowerSyncTask for synchronizing voting power updates and is registered as an internal task with the task definition ID 10001.

Usage

Use the --sync-interval <syncInterval in milliseconds> flag to configure synchronization intervals. For example, --sync-interval 5400000 sets the interval to 1 hour and 30 minutes (equivalent to 5,400,000 milliseconds).

Othentic-cli node aggregator --internal-tasks --sync-interval 5400000

Voting Power Calculation and Syncing Logic

The Voting Power Calculator is responsible for calculating the voting power of operators across Layer 1 (L1) and Layer 2 (L2) blockchains. The task logic contains fetching the voting power from both chains, computing the difference, identifying operators whose voting power has either increased or decreased.

Key Features:

  • Periodic scheduling of the voting power synchronization process.

  • Validation of proposed voting power updates against recalculated values.

  • Broadcasting results through the P2P framework.

Logging & Error Handling

The task logs important events, including scheduling, execution, and validation results, to facilitate debugging and monitoring.

  • Errors encountered during execution are logged using the Logger service.

  • Validation errors are handled by comparing calculated and proposed values.