Operators
Operators in the Cygnus ecosystem are entities responsible for running the infrastructure necessary to support decentralized networks, both within Cygnus and beyond. These operators are registered in the Cygnus protocol, which logs their interactions and maintains a comprehensive registry of operators. This registry includes metadata provided by the operators themselves and data generated through their interactions with the Cygnus protocol.
Registry and Metadata:
Operators register through the Cygnus protocol, which stores various data points including the networks they are involved with, the vaults they are associated with, and their historical interactions like slashing events.
This metadata helps build a detailed profile for each operator, which can be useful for future networks looking to select operators based on reputation and other factors.
Interaction with Vaults:
Operators must opt into networks and vaults to participate in staking and infrastructure provision. This is done by calling the
optIn()method in theNetworkOptInServiceandVaultOptInService.Once opted in, the operator’s stake becomes active and can be allocated by calling
D.setOperatorNetworkLimit(), which is controlled by theOPERATOR_NETWORK_LIMIT_SET_ROLE.
Slashing and Timelocks:
Once an operator opts into both a network and a vault, their stake becomes subject to slashing. The slashing process is managed by the
Smodule within the protocol.A timelock can be applied when allocating a stake to provide additional guarantees to the operators, delaying the activation of the stake until the timelock expires.
Future Vision:
Cygnus aims to enhance its protocol to include more verifiable data and curated credentials about operators. This will allow networks to implement reputation-based operator selection mechanisms, increasing capital efficiency and security. This vision includes operators being able to attract diverse stakes from multiple partners, without needing to set up isolated infrastructure for each one.
Last updated