Skip to content

TaiyiRegistryCoordinator.md

Latest commit

 

History

History
100 lines (70 loc) · 3.87 KB

TaiyiRegistryCoordinator.md

File metadata and controls

100 lines (70 loc) · 3.87 KB

TaiyiRegistryCoordinator

File Notes
TaiyiRegistryCoordinator.sol Canonical registry that maps operators to either EigenLayer operator sets or Symbiotic sub-networks.
TaiyiRegistryCoordinatorStorage.sol Explicit storage slots used by the coordinator.

Motivation

The coordinator unifies the bookkeeping for multiple restaking protocols under a single contract so that:

  • Middleware contracts ( EigenLayer & Symbiotic ) can register / deregister operators through the same interface.
  • Off-chain indexers & challengers have one source of truth for operator ➜ service-type mappings.

The contract implements three public interfaces:

  1. ITaiyiRegistryCoordinator – rich view & helper methods
  2. IAVSRegistrar – minimal EigenLayer interface that AllocationManager expects
  3. OwnableUpgradeable, Pausable, EIP712Upgradeable – access-control & meta-tx support

Data Model

Concept EigenLayer Symbiotic
Service Type Operator Set (uint32) Sub-network (uint96 encoded)
Identifier storage _operatorSets.uint32Sets _operatorSets.uint96Sets
Operator→set mapping _operatorSetMembers32[setId] _operatorSetMembers96[setId]

Each operator keeps a compact OperatorInfo struct:

struct OperatorInfo {
    uint96 operatorId;      // incremental id
    OperatorStatus status;  // REGISTERED / DEREGISTERED / ...
    bytes socket;           // user supplied metadata
}

Restaking protocol of a middleware is tracked in restakingProtocolMap : address → enum {NONE,EIGENLAYER,SYMBIOTIC} and the ID itself encodes the protocol via OperatorSubsetLib.

External Write API

Function Who Description
registerOperator(operator, setIds, data) middleware Route to _registerOperatorForEigenlayer or _registerOperatorForSymbiotic based on msg.sender protocol. Validates min-stake via AllocationManager or local mapping.
deregisterOperator(operator, setIds) middleware Mirrors registration path; emits <OperatorDeregistered> events.
createOperatorSet(id, minStake) EigenLayer middleware (owner) Declare a new operator set (32-bit id).
createSubnetwork(id96, minStake) Symbiotic middleware Declare a sub-network (uint96 = protocol flags << 32
updateSocket(string) operator Update off-chain metadata.

Most mutating functions are gated by Pausable bit-flags (PAUSED_REGISTER_OPERATOR, PAUSED_DEREGISTER_OPERATOR, …).

Flow Diagrams

1️⃣ EigenLayer Path

sequenceDiagram
    participant MW as EigenLayerMiddleware
    participant Coord as TaiyiRegistryCoordinator
    participant Alloc as AllocationManager

    MW->>Coord: registerOperator(operator, [setIds])
    Coord->>Alloc: IAVSRegistrar.registerOperator(...)
    Alloc-->>Coord: callback (on success)
    Coord-->>MW: OperatorRegistered()
Loading

2️⃣ Symbiotic Path

sequenceDiagram
    participant MW as SymbioticNetworkMiddleware
    participant Coord as TaiyiRegistryCoordinator

    MW->>Coord: registerOperator(operator, [subnetworkIds96])
    Note over Coord: stores membership locally (no AllocationManager)
    Coord-->>MW: OperatorRegistered()
Loading

Integration With Slashing

The coordinator is read-only during slashing. LinglongSlasher queries:

  • getOperatorAllocatedOperatorSets to discover in which sets / subnetworks the operator holds stake.
  • getMiddlewareProtocol to decide the slashing handler.

External Links