Operator sets

EigenLayer operator sets have been discussed and designed at length to create more granular roles and permissions for EigenLayer operators and AVS design. For DIN as an AVS, this would mean the node providers would be able to join EigenLayer restaking and specifically be identified for watchers to stake or slash. Each operator set will need to represent a specific service—for example, the watcher service or specific blockchain networks.

Understanding operator sets

Operator sets in DIN represent different blockchain networks that operators can serve. Each set has its own:

• Staking requirements
• Performance metrics
• Slashing conditions
• Infrastructure requirements

Available operator sets

DIN currently supports the following blockchain networks through operator sets:

Set ID	Network Name
2	Ethereum
3	Ethereum-holesky
4	blast-mainnet
5	blast-testnet
6	polygon
7	polygon-testnet
8	optimism-mainnet
9	optimism-sepolia
10	arbitrum-mainnet
11	arbitrum-mainnet-archive
12	arbitrum-sepolia-archive
13	avalanche-mainnet
14	mantle-mainnet
15	mantle-sepolia
16	zksync-mainnet
17	zksync-sepolia
18	bsc-mainnet
19	bsc-testnet
20	starknet-mainnet
21	starknet-sepolia
22	opbnb-mainnet
23	opbnb-testnet
24	base-mainnet
25	base-sepolia
26	scroll-mainnet
27	scroll-sepolia
28	solana-mainnet
29	solana-devnet
30	unichain-mainnet
31	unichain-sepolia
32	Swellchain-mainnet
33	Swellchain-testnet
34	Sei-mainnet
35	Sei-mainnet-archive
36	Hoodi

Check app.din.build for the most up-to-date list and requirements.

Joining operator sets

Operators select which sets to join during onboarding:

1. Assess Capabilities: Evaluate your infrastructure for each network
2. Review Requirements: Check minimum stake and performance standards
3. Select Sets: Choose networks you can reliably support
4. Allocate Stake: Distribute your stake across selected sets
5. Configure Infrastructure: Set up nodes for each network

For detailed instructions, see our Operator Onboarding Guide.

Stake allocation strategies

When joining operator sets, you'll allocate your stake across different strategies:

Available strategies

• stETH (Lido Staked ETH): Earns staking rewards
• WETH (Wrapped ETH): Provides liquidity flexibility
• cbETH (Coinbase Staked ETH): Alternative staking option (mainnet)
• rETH (Rocket Pool ETH): Decentralized staking (mainnet)

Allocation examples

Conservative approach (focus on yield)

• 75% stETH
• 25% WETH

Balanced approach

• 50% stETH
• 50% WETH

Flexible approach (focus on liquidity)

• 25% stETH
• 75% WETH

Performance requirements

Each operator set has specific SLA requirements:

General standards

• Uptime: Greater than 99.9%
• Response Time: Less than 100ms p50
• Availability: Continuous (every day)
• Data Freshness: Real-time

Network-specific requirements

Different networks may have additional requirements:

• Ethereum: Archive node access
• L2s: Sequencer connectivity
• Alt-L1s: Native token holdings

Rewards distribution

Rewards are calculated per operator set based on:

1. Request Volume: Number of RPC requests served
2. Performance Metrics: SLA compliance
3. Stake Weight: Your stake relative to total
4. Network Demand: Overall usage of the network

Slashing conditions

Each operator set can have specific slashing conditions:

• Downtime: Extended unavailability
• Latency: Consistent slow responses
• Invalid Data: Serving incorrect information
• Liveness: Failure to respond

See Slashing and Rewards for detailed information.

Managing multiple sets

Best practices

1. Start Small: Begin with 1-2 sets you know well
2. Monitor Performance: Ensure service level agreement compliance before adding more
3. Scale Gradually: Add sets as infrastructure allows
4. Maintain Balance: Don't overextend resources

Infrastructure considerations

• Dedicated Nodes: Run separate nodes per network
• Monitoring: Track each set independently
• Redundancy: Backup systems per network
• Team Expertise: Ensure knowledge for each chain

Future developments

Upcoming features

• Dynamic stake reallocation
• Cross-set performance bonuses
• Set-specific governance rights
• Advanced slashing parameters

Planned operator sets

• Additional L2 solutions
• Cosmos ecosystem chains
• Solana and other alt-L1s
• Application-specific chains

Getting started

Ready to join operator sets? Follow these steps:

1. Review Requirements: Check our Prerequisites
2. Begin Onboarding: Start with Step 1: Register
3. Select Sets: Choose during the allowlisting process
4. Allocate Stake: Configure in Step 2