How othentic-labs/core-contracts works
Project type and purpose
– This is a Solidity-based “distributed systems” framework built with Foundry, targeting Ethereum-style Layer 1 (L1) and Layer 2 (L2) networks.
– Its purpose is to provide on‐chain governance (AvsGovernance on L1) and task/attestation coordination (AttestationCenter on L2), with cross‐chain messaging powered by LayerZero.
File structure
– Top-level:
• foundry.toml, remappings.txt – Foundry build/test config
• lib/ – Git submodules for dependencies (LayerZero, OpenZeppelin, eigenlayer, etc.)
• src/ – project contracts, subdivided into NetworkManagement and lz (LayerZero) packages
• audits/ – security reports
– Under src/:
• NetworkManagement/Common – shared interfaces/types
• NetworkManagement/L1 & L2 – on‐chain logic for each layer
• lz/ – LayerZero v1 & v2 abstraction, message handlers, utils, and interfaces
Key insights from README
– Package breakdown:
• L1: AvsGovernance + l1MessageHandler
• L2: AttestationCenter, OBLS, BN256G2 + l2MessageHandler
• lz: cross-chain messaging layer
– Contracts talk to each other only via LayerZero endpoints to overcome on-chain isolation
a. Main components
1. Layer 1 chain node and AvsGovernance (L1 smart contract)
2. L1MessageHandler (LayerZero endpoint on L1)
3. LayerZero Relayer / Endpoint (off-chain infrastructure)
4. Layer 2 chain node and AttestationCenter (L2 smart contract)
5. L2MessageHandler (LayerZero endpoint on L2)
6. Ancillary L2 contracts: OBLS, BN256G2
7. Shared on‐chain libraries (OpenZeppelin, Forge-std) shown as external dependencies
b. Relationships and interactions
• AvsGovernance ↔ L1MessageHandler (internal call)
• L1MessageHandler → LayerZero Endpoint → L2MessageHandler → AttestationCenter (cross‐chain message)
• AttestationCenter ↔ OBLS/BN256G2 (task validation & multisig)
• L2MessageHandler → LayerZero Endpoint → L1MessageHandler → AvsGovernance (return messages)
c. Architectural patterns and design principles
– Layered separation: governance vs. attestation
– Modular contracts with clear interfaces under Common/NetworkManagement
– Cross‐chain “adapter” pattern (message handlers) isolating protocol logic from messaging
– Use of industry-standard libs via git submodules
d. Technologies, frameworks, and libraries
– Foundry (forge) build/test
– Solidity (contracts under src/)
– LayerZero v1/v2 (in lib/LayerZero-v2) for messaging
– OpenZeppelin contracts (in lib/)
– EigenLayer, onchain-firewall, OBLS, BN256G2