Search

Search for projects by name or address

Syndicate Chain logo
Syndicate Chain

Badges

About

Syndicate Chain is an Arbitrum Orbit rollup on Ethereum using SYND as its native gas token. It serves as the primary settlement layer for the Syndicate ecosystem.


  • Total Value SecuredTVS
    No data
  • Past day UOPSDaily UOPS
    No data
  • Gas token
    SYND
  • Type
    Other

  • Purpose
    Universal
  • Chain ID
    510

  • Tokens breakdown

    Value secured breakdown

    View TVS breakdown
    Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    Syndicate Chain is an Arbitrum Orbit rollup on Ethereum using SYND as its native gas token. It serves as the primary settlement layer for the Syndicate ecosystem.

    Why is the project listed in others?

    There are less than 5 external actors that can submit challenges

    Consequence: projects without a sufficiently decentralized set of challengers rely on few entities to safely update the state. A small set of challengers can collude with the proposer to finalize an invalid state, which can cause loss of funds.

    Learn more about the recategorisation here.

    2025 Jul 29 — 2026 Mar 24

    Past Day UOPS
    No data
    Past Day Ops count
    No data
    Max. UOPS
    <0.01
    2025 Sep 04
    Past day UOPS/TPS Ratio
    No data

    The section shows the operating costs that L2s pay to Ethereum.


    2025 Jul 29 — 2026 Mar 24


    Total cost
    $5.39 K
    Avg cost per L2 UOP
    $0.460992
    Avg cost per day
    $22.58

    This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toEthereumEthereum.


    2026 Feb 06 — Mar 24


    Data posted
    210.88 MiB
    Avg size per day
    4.39 MiB
    Avg size per L2 UOP
    No data

    This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule.

    No ongoing anomalies detected

    Avg. tx data subs. interval
    Avg. state updates interval
    Past 30 days anomalies
    99% normal uptime

    Last 30 day anomalies

    All liveness anomalies detected for this project in the last 30 days, helping you review recent downtime and availability issues.

    No State updates were performed for 1h 17m (from 2026 Feb 25, 16:34 UTC until 2026 Feb 25, 17:51 UTC). These typically occur every 1h 51s on average.

    This project includes unverified contracts.
    (CRITICAL)
    Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.
    This project includes unverified contracts.
    (CRITICAL)
    Fraud proof system is fully deployed but is not yet permissionless as it requires Validators to be whitelisted.
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Self sequence

    In the event of a sequencer failure, users can force transactions to be included in the project’s chain by sending them to L1. There can be up to a 4d delay on this operation.

    State validation
    Fraud proofs (INT)

    No actor outside of the single Proposer can submit fraud proofs. Interactive proofs (INT) require multiple transactions over time to resolve. The challenge protocol can be subject to delay attacks. There is a 7d challenge period.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    None

    There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.

    Proposer failure
    Self propose

    Anyone can become a Proposer after 1mo 5d of inactivity from the currently whitelisted Proposers.

    Syndicate Chain
    Syndicate Chain is not even a
    Stage 0
    project.
    The requirement for available node software is under review

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.

    All data required for proofs is published on chain

    All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.

    1. Sequencing followed by deterministic execution - Arbitrum documentation
    2. SequencerInbox.sol - source code, addSequencerL2BatchFromOrigin function
    Learn more about the DA layer here: Ethereum logoEthereum
    A diagram of the state validation
    A diagram of the state validation

    Updates to the system state can be proposed and challenged by a set of whitelisted validators. If a state root passes the challenge period, it is optimistically considered correct and made actionable for withdrawals.


    State root proposals

    Whitelisted validators propose state roots as children of a previous state root. A state root can have multiple conflicting children. This structure forms a graph, and therefore, in the contracts, state roots are referred to as nodes. Each proposal requires a stake, currently set to 0.1 ETH, that can be slashed if the proposal is proven incorrect via a fraud proof. Stakes can be moved from one node to one of its children, either by calling stakeOnExistingNode or stakeOnNewNode. New nodes cannot be created faster than the minimum assertion period by the same validator, currently set to 15m. The oldest unconfirmed node can be confirmed if the challenge period has passed and there are no siblings, and rejected if the parent is not a confirmed node or if the challenge period has passed and no one is staked on it.

    • Funds can be stolen if none of the whitelisted verifiers checks the published state. Fraud proofs assume at least one honest and able validator (CRITICAL).

    1. How is fraud proven - Arbitrum documentation FAQ
    Challenges

    A challenge can be started between two siblings, i.e. two different state roots that share the same parent, by calling the startChallenge function. Validators cannot be in more than one challenge at the same time, meaning that the protocol operates with partial concurrency. Since each challenge lasts 7d, this implies that the protocol can be subject to delay attacks, where a malicious actor can delay withdrawals as long as they are willing to pay the cost of losing their stakes. If the protocol is delayed attacked, the new stake requirement increases exponentially for each challenge period of delay. Challenges are played via a bisection game, where asserter and challenger play together to find the first instruction of disagreement. Such instruction is then executed onchain in the WASM OneStepProver contract to determine the winner, who then gets half of the stake of the loser. As said before, a state root is rejected only when no one left is staked on it. The protocol does not enforces valid bisections, meaning that actors can propose correct initial claim and then provide incorrect midpoints.

    1. Fraud Proof Wars: Arbitrum Classic

    Program Hashes

    Name
    Hash
    Repository
    Verification
    Used in
    0x2c9a...3ea7
    Code unknown
    None
    Syndicate Chain logo

    Past upgrades

    The metrics include upgrades on the currently used proxy contracts. Historical proxy contracts and changes of such are not included.

    Count of upgrades
    99
    Last upgrade
    1mo 23d ago
    Avg upgrade interval
    5mo 27d

    The system has a centralized sequencer

    While forcing transaction is open to anyone the system employs a privileged sequencer that has priority for submitting transaction batches and ordering transactions.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    1. Sequencer - Arbitrum documentation

    Users can force any transaction

    Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly. After a delay of 4d in which a Sequencer has failed to include a transaction that was directly posted to the smart contract, it can be forcefully included by anyone on the host chain, which finalizes its ordering.

    1. SequencerInbox.sol - source code, forceInclusion function
    2. Sequencer Isn't Doing Its Job - Arbitrum documentation

    Delayed forced transactions

    To force transactions from the host chain, users must first enqueue “delayed” messages in the “delayed” inbox of the Bridge contract. Only authorized Inboxes are allowed to enqueue delayed messages, and the so-called Inbox contract is the one used as the entry point by calling the sendMessage or sendMessageFromOrigin functions. If the centralized sequencer doesn’t process the request within some time bound, users can call the forceInclusion function on the SequencerInbox contract to include the message in the canonical chain. The time bound is hardcoded to be 4d.

    Regular messaging

    The user initiates L2->L1 messages by submitting a regular transaction on this chain. When the block containing that transaction is settled, the message becomes available for processing on L1. The process of block finalization usually takes several days to complete.

    1. Transaction lifecycle - Arbitrum documentation
    2. L2 to L1 Messages - Arbitrum documentation
    3. Mainnet for everyone - Arbitrum Blog

    Autonomous exit

    Users can (eventually) exit the system by pushing the transaction on L1 and providing the corresponding state root. The only way to prevent such withdrawal is via an upgrade.

    EVM compatible smart contracts are supported

    Arbitrum One uses Nitro technology that allows running fraud proofs by executing EVM code on top of WASM.

    1. Inside Arbitrum Nitro
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    Roles:

    SequencerEOA 10

    Can submit transaction batches or commitments to the SequencerInbox contract on the host chain.

    ValidatorEOA 12

    Can propose new state roots (called nodes) and challenge state roots on the host chain.

    DisperserEOA 9

    Can disperse EigenDA blobs to the EigenDA node operators.

    Used in:
    RelayerEOA 8

    Can store and serve both unencoded blobs as well as encoded chunks.

    Used in:

    Actors:

    EigenLayerOperationsMultisig20x4618…533F

    A Multisig with 3/5 threshold.

    • Can upgrade with 10d delay
      • swETH-Strategy
      • TaskMailbox
      • AVSDirectory
      • ankrETH-Strategy
      • rETH-Strategy
      • PermissionController
      • ProtocolRegistry
      • METH-Strategy
      • DelegationManager
      • BN254CertificateVerifier
      • cbETH-Strategy
      • KeyRegistrar
      • OperatorTableUpdater
      • osETH-Strategy
      • StrategyFactory
      • RewardsCoordinator
      • wBETH-Strategy
      • StrategyManager
      • sfrxETH-Strategy
      • EigenPodManager
      • CrossChainRegistry
      • stETH-Strategy
      • AllocationManager
      • ETHx-Strategy
      • OETH-Strategy
      • bEIGEN-Strategy
      • RiverV1-Strategy
      • ECDSACertificateVerifier
      • EIGEN token
      • ReleaseManager
    • Can upgrade with 24d delay
      • bEIGEN token
    • Can interact with TimelockControllerBeigen
      • executes scheduled operations after the delay
    • Can interact with TimelockControllerOwning
      • executes scheduled operations after the delay
    Used in:
    EigenLayerOperationsMultisig0xBE16…3e90

    A Multisig with 3/6 threshold.

    • Can upgrade with 10d delay
      • swETH-Strategy
      • TaskMailbox
      • AVSDirectory
      • ankrETH-Strategy
      • rETH-Strategy
      • PermissionController
      • ProtocolRegistry
      • METH-Strategy
      • DelegationManager
      • BN254CertificateVerifier
      • cbETH-Strategy
      • KeyRegistrar
      • OperatorTableUpdater
      • osETH-Strategy
      • StrategyFactory
      • RewardsCoordinator
      • wBETH-Strategy
      • StrategyManager
      • sfrxETH-Strategy
      • EigenPodManager
      • CrossChainRegistry
      • stETH-Strategy
      • AllocationManager
      • ETHx-Strategy
      • OETH-Strategy
      • bEIGEN-Strategy
      • RiverV1-Strategy
      • ECDSACertificateVerifier
      • EIGEN token
      • ReleaseManager
    • Can upgrade with 24d delay
      • bEIGEN token
    • Can interact with TimelockControllerBeigen
      • can cancel scheduled operations
    • Can interact with TimelockControllerOwning
      • can cancel scheduled operations
    Used in:
    EigenLayerCommunityMultisig0xFEA4…c598

    A Multisig with 9/13 threshold. Member of EigenLayerOwningMultisig, EigenLayerBeigenOwningMultisig.

    • Can upgrade with no delay
      • swETH-Strategy
      • TaskMailbox
      • AVSDirectory
      • ankrETH-Strategy
      • rETH-Strategy
      • PermissionController
      • ProtocolRegistry
      • METH-Strategy
      • DelegationManager
      • BN254CertificateVerifier
      • cbETH-Strategy
      • KeyRegistrar
      • OperatorTableUpdater
      • osETH-Strategy
      • StrategyFactory
      • RewardsCoordinator
      • wBETH-Strategy
      • bEIGEN token
      • StrategyManager
      • sfrxETH-Strategy
      • EigenPodManager
      • CrossChainRegistry
      • stETH-Strategy
      • AllocationManager
      • ETHx-Strategy
      • OETH-Strategy
      • bEIGEN-Strategy
      • RiverV1-Strategy
      • ECDSACertificateVerifier
      • EIGEN token
      • ReleaseManager
    Used in:
    EigenDAOperationsMultisig0x0027…92D5

    A Multisig with 3/5 threshold.

    • Can upgrade with no delay
      • StakeRegistry
      • BLSApkRegistry
      • RegistryCoordinator
      • EjectionManager
      • SocketRegistry
      • EigenDADisperserRegistry
      • EigenDAServiceManager
      • PaymentVault
      • IndexRegistry
      • EigenDARelayRegistry
      • EigenDAThresholdRegistry
    • Can interact with RegistryCoordinator
      • can add and remove strategies
    • Can interact with EigenDAServiceManager
      • can transfer ownership of the contract, update the metadata URI, set reward initiator and set batch confirmer
    Used in:
    • Can upgrade with no delay
      • SequencerInbox
      • Bridge
      • GatewayRouter
      • Inbox
      • ERC20Gateway
      • RollupEventInbox
      • ChallengeManager
      • Outbox
      • UpgradeExecutor
    PauserRegistry0x0c43…7060

    Defines and stores pauser and unpauser roles for EigenDA contracts.

    • Can interact with EigenDAServiceManager
    Used in:
    EigenLayerRewardsInitiatorMultisig0x178e…1b8A

    A Multisig with 3/4 threshold.

    • Can interact with EigenDAServiceManager
      • can create rewards submissions
    Used in:
    EigenDA Multisig0x3384…4B34

    A Multisig with 3/8 threshold.

    • Can interact with EjectionManager
      • can eject DA operators from a quorum
    Used in:
    Alchemy Multisig 10xA4fB…bF1d

    A Multisig with 5/8 threshold.

    • Can upgrade with no delay
      • RollupProxy
    Used in:
    EigenLayerOwningMultisig0x369e…9111

    A Multisig with 1/2 threshold.

    Used in:
    EigenLayerPauserMultisig0x5050…2390

    A Multisig with 1/7 threshold.

    Used in:

    A Multisig with 1/1 threshold. Member of EigenLayerCommunityMultisig.

    Participants (1):

    0x5e6a…d3B5
    Used in:
    EigenLayerBeigenOwningMultisig0x942e…D67d

    A Multisig with 1/2 threshold.

    Used in:

    A Multisig with 2/9 threshold. Member of EigenLayerPauserMultisig.

    Used in:
    EOA 1, EOA 2 and EOA 5 (3)0x454E…ca4e0x5A49…61ED0x8ED8…84D8
    • Can interact with EigenDAServiceManager
    • Can upgrade with no delay
      • EigenDAThresholdRegistry
    EOA 4 and EOA 6 (2)0x8642…72360xD2Ee…8eA8
    • Can interact with EjectionManager
      • can eject DA operators from a quorum
    • Can interact with RegistryCoordinator
      • can approve the replacement of churned operators from a quorum
    Used in:
    • A DA Relayer - acting directly
    Used in:
    • A Disperser - acting directly
    Used in:
    • Can upgrade with no delay
      • RollupProxy
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    Contract that allows challenging state roots. Can be called through the RollupProxy by Validators or the UpgradeExecutor.

    • Roles:
      • admin: The source code of this contract is not verified on Etherscan.
    Can be upgraded by:

    Keeps track of the total stake of each operator.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:

    Keeps track of the BLS public keys of each operator and the quorum aggregated keys.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:

    Operators register here with an AVS The coordinator has three registries 1) a StakeRegistry that keeps track of operators’ stakes, 2) a BLSApkRegistry that keeps track of operators’ BLS public keys and aggregate BLS public keys for each quorum, 3) an IndexRegistry that keeps track of an ordered list of operators for each quorum.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
      • churnApprover: EOA 7
      • owner: EigenDAOperationsMultisig
    Proxy used in:

    Contract used for ejection of operators from the RegistryCoordinator for violating the Service Legal Agreement (SLA).

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
      • ejectors: EOA 4, EOA 6, EigenDA Multisig
    Proxy used in:
    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:

    Registry for EigenDA disperser info such as disperser key to address mapping.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
      • dispersers: EOA 9
    Proxy used in:

    Bridge contract that accepts blob batches data availability attestations. Batches availability is attested by EigenDA operators signatures and relayed to the service manager contract by the EigenDA disperser.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
      • batchConfirmers: EOA 1, EOA 2, EOA 5
      • owner: EigenDAOperationsMultisig
      • pauserRegistry: PauserRegistry
      • rewardsInitiator: EigenLayerRewardsInitiatorMultisig
    Proxy used in:

    Registry of EigenDA threshold (i.e, adversary and confirmation threshold percentage for a quorum)

    • Roles:
      • admin: ProxyAdmin; ultimately EOA 3
    Can be upgraded by:

    Entrypoint for making reservations and on demand payments for EigenDA.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:

    A registry contract that keeps track of an ordered list of operators for each quorum.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:

    Registry for EigenDA relay keys, maps key to address.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
      • relayers: EOA 8
    Proxy used in:

    Registry of EigenDA threshold (i.e, adversary and confirmation threshold percentage for a quorum)

    • Roles:
      • admin: ProxyAdmin; ultimately EigenDAOperationsMultisig
    Proxy used in:
    RewardAllStakersActionGenerator0x0903…E4E5

    Generates calldata for the TokenHopper to mint EIGEN and send it to the RewardsCoordinator for distribution to all stakers.

    Implementation used in:
    AllocationManagerView0x0D4e…4a34

    Read-only view contract that exposes query functions for the AllocationManager, allowing external callers to look up operator stake allocations, magnitudes, operator sets, and slashable/redistributable status.

    Implementation used in:
    StrategiesBeacon0x0ed6…2fE9

    UpgradeableBeacon managing the single implementation for all strategies deployed via StrategyFactory.

    Implementation used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Task lifecycle manager where users create tasks with fee payments directed at specific executor operator sets, and executors submit results verified via BN254 or ECDSA certificate verification, with fee distribution on successful verification and refunds on task expiration.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Contract that enables AVSs and operators to delegate the ability to call certain core contract functions to other addresses.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Admin-controlled on-chain registry that tracks all EigenLayer protocol contract deployments (addresses, names, configs, and versioning) and provides a pauseAll function to pause every registered pausable contract in the protocol.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    TokenHopper0x3374…7E7d

    Minter of the bEIGEN (and thus EIGEN) token. Can execute a predefined payload in predefined intervals (configured by the Owner).

    Implementation used in:

    The DelegationManager contract is responsible for registering EigenLayer operators and managing the EigenLayer strategies delegations. The EigenDA StakeRegistry contract reads from the DelegationManager to track the total stake of each EigenDA operator.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Verifies BLS (BN254 curve) certificates for EigenLayer operator sets by computing the aggregate public key of signers, performing pairing-based signature verification, and returning signed-stake weights for quorum threshold validation.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    Implementation used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Manages the registration and deregistration of operator cryptographic keys (ECDSA or BN254/BLS) for specific operator sets, enforcing signature-based proof of key ownership and global uniqueness of keys across the protocol.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Central coordinator for EigenLayer’s operator table system: accepts BN254-certified global Merkle table roots from a designated generator operator set, then allows Merkle proof submissions to push per-operator-set tables into the certificate verifier contracts.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    UpgradeableBeacon0x5a2a…9073

    UpgradeableBeacon managing the single implementation for all strategies deployed via StrategyFactory.

    Implementation used in:

    Factory contract for permissionless strategy creation via beacon proxies.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    TimelockControllerBeigen0x7381…bc53

    A timelock that allows scheduling calls and executing or cancelling them with a delay. Member of EigenLayerBeigenOwningMultisig.

    • Roles:
      • cancellers: EigenLayerOperationsMultisig
      • executors: EigenLayerOperationsMultisig2
      • proposers: EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Implementation used in:

    Manages the distribution of rewards (arbitrary tokens, EIGEN) to restakers and commission to operators.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    The token backing EIGEN and used for intersubjective staking.

    • Roles:
      • admin: ProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    The StrategyManager contract is responsible for managing the EigenLayer token strategies. Each EigenDA quorum has at least one strategy that defines the operators quorum stake.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Allows AVSs to create generation reservations that configure and schedule the transport of operator tables (stake weight data) from L1 to whitelisted L2 chains, managing per-operator-set configs such as staleness periods and operator table calculators.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Contract used to create Operator Sets, and used by Operators to register to them. The Allocation Manager tracks allocation of stake to a Operator Set, and enables AVSs to slash that stake.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    PauserRegistry0xB876…2806

    Defines and stores pauser and unpauser roles for EigenLayer contracts.

    • Roles:
      • pausers: EigenLayerOperationsMultisig, EigenLayerOwningMultisig, EigenLayerPauserMultisig, ProtocolRegistry
    Implementation used in:
    TimelockControllerOwning0xC06F…Aa2d

    A timelock that allows scheduling calls and executing or cancelling them with a delay. Member of EigenLayerOwningMultisig.

    • Roles:
      • cancellers: EigenLayerOperationsMultisig
      • executors: EigenLayerOperationsMultisig2
      • proposers: EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Implementation used in:

    Verifies ECDSA-based certificates for EigenLayer operator sets by recovering signer addresses from concatenated signatures, confirming each signer is a registered operator, and tallying their stake weights against quorum thresholds.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:
    StrategyBase0xd33A…2780

    A strategy implementation allowing to deposit a specific token as a restakable asset.

    Implementation used in:

    The EIGEN token can be socially forked to slash operators for data withholding attacks (and other intersubjectively attributable faults). EIGEN is a wrapper over a second token, bEIGEN, which will be used solely for intersubjective staking. Forking EIGEN means changing the canonical implementation of the bEIGEN token in the EIGEN token contract.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Manages software release lifecycle for EigenLayer operator sets, allowing AVS owners to publish versioned releases (containing artifact digests, registry URLs, and upgrade-by deadlines) and metadata URIs that operators can query for required software versions.

    • Roles:
      • admin: EigenLayerProxyAdmin; ultimately EigenLayerCommunityMultisig, EigenLayerOperationsMultisig, EigenLayerOperationsMultisig2
    Proxy used in:

    Central contract defining the access control permissions for upgrading the system contract implementations.

    • Roles:
      • admin:
      • executors: Alchemy Multisig 1, EOA 11 The source code of this contract is not verified on Etherscan.
    Can be upgraded by:

    Facilitates sending L1 to L2 messages like depositing ETH, but does not escrow funds.

    • Roles:
      • admin: The source code of this contract is not verified on Etherscan.
    Can be upgraded by:

    Escrows deposited ERC-20 assets for the canonical Bridge. Upon depositing, a generic token representation will be minted at the destination. Withdrawals are initiated by the Outbox contract.

    • Roles:
      • admin:

    All supported tokens in this escrow are included in the value secured calculation.

    Can be upgraded by:
    Implementation used in:

    Facilitates L2 to L1 contract calls: Messages initiated from L2 (for example withdrawal messages) eventually resolve in execution on L1.

    • Roles:
      • admin: The source code of this contract is not verified on Etherscan.
    Can be upgraded by:

    This routing contract maps tokens to the correct escrow (gateway) to be then bridged with canonical messaging.

    • Roles:
      • admin:
    Can be upgraded by:
    Implementation used in:
    • Roles:
      • admin:
      • batchPosters: EOA 10 The source code of this contract is not verified on Etherscan.
    Can be upgraded by:
    Syndicate Token0x1bAB…614E
    OneStepProver00x2420…6b2F

    One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.

    OneStepProverMemory0x27CD…6Ec6

    One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.

    • Roles:
      • admin: The source code of this contract is not verified on Etherscan.
    The following tokens are included in the value secured calculation:
    SYND token logo
    Can be upgraded by:
    • Roles:
      • admin: UpgradeExecutor; ultimately Alchemy Multisig 1, EOA 11
      • validators: EOA 12 The source code of this contract is not verified on Etherscan.
    OneStepProverHostIo0x6D25…a2D7
    OneStepProverMath0x7847…4235

    One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.

    EigenDACertVerifier0x787c…D1eb
    ProxyAdmin0x817B…0c66
    • Roles:
      • owner: EOA 3
    ProxyAdmin0x8247…2E99
    • Roles:
      • owner: EigenDAOperationsMultisig
    Implementation used in:

    Helper contract sending configuration data over the bridge during the systems initialization.

    • Roles:
      • admin: The source code of this contract is not verified on Etherscan.
    Can be upgraded by:
    OneStepProofEntry0xa8aA…5EC8

    One of the modular contracts used for the last step of a fraud proof, which is simulated inside a WASM virtual machine.

    ValidatorUtils0xAa1E…8cC0

    This contract implements view only utilities for validators.

    ProxyAdmin0x3f5A…5CC9
    • Roles:
      • owner: EigenLayerBeigenOwningMultisig
    Implementation used in:
    EigenLayerProxyAdmin0x8b95…2444
    • Roles:
      • owner: EigenLayerOwningMultisig
    Implementation used in:

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).

    • Funds can be stolen if the source code of unverified contracts contains malicious code (CRITICAL).

    Program Hashes

    Name
    Hash
    Repository
    Verification
    Used in
    0x2c9a...3ea7
    Code unknown
    None
    Syndicate Chain logo