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
    • 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
    • CLI Command Reference
    • Explainers
      • Networking
      • Production Guidelines
      • Governance Multisig
  • External
    • Github
    • Oracle Example (JS)
    • Oracle Example (Go)
    • Oracle Example (Rust)
    • PRNG Example
Powered by GitBook
On this page
  • Overview
  • Contract Addresses
  • Core Functions
  • L1 Message Handler
  • L2 Message Handler
  1. AVS Framework
  2. Smart Contracts

Message Handlers

PreviousOthentic RegistryNextOthentic Consensus

Last updated 3 months ago

Overview

The L1MessageHandler and L2MessageHandler contracts represent an abstraction for cross-chain message communication used within the Othentic Stack. Each AVS deploys its own message handlers to facilitate message-passing between Layer 1 and Layer 2 blockchains. These handlers play a critical role in ensuring seamless and secure communication across different layers.

Leveraging LayerZero messaging protocol, L1MessageHandler, and L2MessageHandler in conjunction with Decentralized Verifier Networks (DVNs), the Othentic Stack enables message-passing interactions between different layers such as L1 and L2.

Contract Addresses

By executing othentic-cli network deploy command, the L1 and L2 Message Handlers are deployed. The contract addresses can be obtained from the L1MessageHandlerDeployed and L2MessageHandlerDeployed events, emitted in the respective L1 and L2 transactions.

To avoid failed message executions, ensure that Message Handler Contracts are funded with the native tokens of their respective chains.

Core Functions

The primary goal of the handler contracts is to communicate infrequent operations such as the registration and deregistration of Operators, slashing events, and the distribution of rewards payments.

L1 Message Handler

Access Control: Only the AVS governance contract can send messages from L1.

Functionality:

  • AVS governance contract calls the L1 messageHandler to notify L2 about processed payments and Operator status updates.

  • Message Processing: Implements _lzReceive method to handle incoming messages from L2, including:

    • Payment request

    • Batch Payment request

L2 Message Handler

Access Control: Only the Attestation Center contract can send messages from L2.

Functionality:

  • The Attestation Center contract calls the L2MessageHandler to forward payment or slashing requests to L1.

  • Message Processing: Implements _lzReceive method to handle incoming messages from L1, including:

    • Operator registration

    • Operator de-registration

    • Payment success

    • Batch payment success