Enable Slashing

The Othentic CLI enables you to configure slashing for an Operator. When slashing is activated for an AVS, each Operator must allocate Unique Stake in order to enable slashing.

Prerequisites

• Othentic CLI installed

• The AVS Governance contract address

• The Operator is part of the AVS's Operator Set

• Slashing is enabled in the AVS

1

Set Allocation Delay

The allocation delay defines how long newly allocated stake must wait before becoming slashable. You can set this to 0 or any number of blocks.

Call setAllocationDelay function on the Allocation Manager Contract.

The delay itself takes 17.5 days (as per ALLOCATION_CONFIGURATION_DELAY) to become active.

2

Wait for the Allocation Delay

Wait for this configuration period to complete.

3

Check Minimum Slashable Requirement

Check with the AVS team if a minimum slashable stake amount has been configured. You must allocate at least that amount or more in the next step to successfully enable slashing.

4

Allocate unique stake

Once the delay has taken effect, allocate a unique stake to the AVS using the following command:

otcli operator allocate 

Read More

• CLI Reference: Allocate Unique Stake

5

Enable Slashing Challenge Proof Submission

If the AVS has enabled the Incorrect Attestation or Double Attestation slashing conditions, set the --slashing-challenger flag to earn the Challenge System rewards when running the Operator nodes as specified in the respective attester and aggregator CLI commands.