# Operator Registration & Incentive System

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**:

1. 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.
2. 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**:

1. Operators must opt into networks and vaults to participate in staking and infrastructure provision. This is done by calling the `optIn()` method in the `NetworkOptInService` and `VaultOptInService`.
2. Once opted in, the operator’s stake becomes active and can be allocated by calling `D.setOperatorNetworkLimit()`, which is controlled by the `OPERATOR_NETWORK_LIMIT_SET_ROLE`.

### **Slashing and Timelocks**:

1. Once an operator opts into both a network and a vault, their stake becomes subject to slashing. The slashing process is managed by the `S` module within the protocol.
2. 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.cygnus.finance/whitepaper/cygnus-omnichain-liquidity-validation-system-lvs/operator-registration-and-incentive-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.