Introduction

A Curator is responsible for managing a Vault and its delegation strategy, distributing users' stake across different L1s while balancing risk and rewards. They play a crucial role in determining how pooled stake is allocated and managed.

Curator-Managed Contracts

Suzaku Vaults

The Vault VaultTokenized.sol (opens in a new tab) is an upgradable contract. It's the core component that converts deposited Collateral into ERC20-like shares representing each user's stake. It provides Curators with the ability to:

• Set deposit and withdrawal rules and limits at deployment
• Configure Vault epochs that determine withdrawal timelines
• Manage stake delegation across operators and Avalanche L1s via the Delegator contract
• Track historical records of stake and share balances

This design allows Curators to manage user funds safely while directing stake to validators.

Delegator Contract

The Delegator contract manages how pooled stake from Vaults is distributed across L1 networks and operators. It calculates effective stake per operator to ensure optimal allocation of resources.

The implementation includes:

• BaseDelegator.sol (opens in a new tab): Provides core functionality with checkpointing for historical records
• L1RestakeDelegator.sol (opens in a new tab): Extends the base contract with specific implementation

Key functions include:

• setL1Limit: Controls how much stake goes to each L1
• setOperatorL1Shares: Determines stake allocation per operator

The contract calculates effective stake based on Vault active stake, L1 limits, and operator share ratios, while integrating with opt-in services and registries to verify eligible operators and L1s. Security is maintained through role-based permissions.

Curator-Accessible Contracts

Permissionless contracts

• Vault Factory: This contract is responsible for deploying new Vaults and managing their lifecycle. It ensures that only approved implementations are used and maintains a registry of all Vault entities. (VaultFactory.sol (opens in a new tab))

• Delegator Factory: Whitelists delegator implementations. A new implementation contract—with, for example, new slashing logic or shares distribution logic—must be whitelisted in the official Delegator Factory before being used. (DelegatorFactory.sol (opens in a new tab))

• Operator-Vault Optin service: Actively used when a Vault registers to determine which operators it wants to work with. This service facilitates the permissionless opt-in of operators by Vaults. OperatorVaultOptInService.sol (opens in a new tab)

• Operator Registry: A permissionless registry that records and manages eligible operators. It maintains a list of operators that Curators can delegate stake to. (OperatorRegistry.sol (opens in a new tab))

• L1 Registry: A permissionless registry that records and manages eligible Avalanche-based L1 networks. Curators can delegate stake from their Vaults to these registered L1s. (L1Registry.sol (opens in a new tab))

External Permissioned Contracts

• Vault Manager: This contract manages the registration of Vaults by the L1, sets maximum stake limits, and ensures Vaults comply with the network's operational parameters. (MiddlewareVaultManager.sol (opens in a new tab))

Integration Flow

A high-level checklist for integrating a new Vault into Suzaku: