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
  • Features
  • Core Functions
  • 1. Governance Management
  • 2. Default Strategies Lookup
  • 3. Operator Share & Voting Power Calculations
  1. AVS Framework
  2. Smart Contracts

Othentic Registry

PreviousOBLSNextMessage Handlers

Last updated 12 days ago

Overview

The Othentic Registry is a singleton smart contract on L1 that facilitates the integration with shared security protocols and AVSs. The contract manages the registration and interacts with key components such as the Slasher, Delegation Manager, and Strategy Manager.

Contract Addresses

The Othentic registry contract is deployed on the following L1 chains.

  • Holesky

  • Ethereum

Features

Integration with shared security protocol (EigenLayer) interfaces The contract uses IOthenticRegistry interface to manage staking, delegation, and tracking shares for operators and strategies.

Staking Contract Lookup A multi-chain-aware strategy lookup system is built in, supporting Ethereum mainnet and specific testnets.

Dynamic Voting Power Consensus In the shared security environment, the Operator's voting power is dynamic and proportional to the amount of re-stake assets locked on Layer 1. The Othentic Registry contract calculates each operator's voting power across multiple shared security protocols, such as EigenLayer and Babylon.

Core Functions

1. Governance Management

registerAvs: Registers an AVS governance.

Parameter
type
description

_avsName

string (memory)

Name of the AVS

2. Default Strategies Lookup

getDefaultStrategies: Returns default strategies based on the chain ID (Mainnet, EigenLayer testnet, or Hardhat testnet).

Parameter
Type
Description

_chainid

uint256

Chain Id

3. Operator Share & Voting Power Calculations

The Othentic registry relies on the DelegationManager contract to manage operator shares and voting power. Here’s a detailed explanation of the relevant functions:

getVotingPower: Calculates voting power based on assigned shares and multipliers.

Parameter
Type
Description

_operator

address

Operator address

_strategyMultipliers

StrategyMultiplier[]

Strategy multiplier

isValidStakeAmount: Verifies if an operator has the required minimum shares for given strategies.

Parameter
Type
Description

_operator

address

Operator address

_minStakePerStakingContracts

StrategyShares[]

Strategy shares

_avsGovernance

address

AVS governance address

getOperatorRestakedStrategies: This function returns Operator shares for specific strategies.

Parameter
Type
Description

_operator

address

Operator address

_allStrategies

address[]

Strategy addresses

_avsGovernance

address

AVS governance address