Skip to content

Mainnet SlashingManager has no slash policies configured #2012

Description

@hmzakhalid

Summary

The mainnet SlashingManager has no slash policies, so no slash can execute on mainnet.

Evidence (checked 2026-09-25, block 26,057,073)

  • SlashingManager 0x974E865B1BB24AF2a9ef8204AdEA9251Cc7C5FD9 has 7 events in its history: RoleGranted (2), RoleAdminChanged, and 4 registry/refund-manager setters. It has no SlashPolicyUpdated event.
  • getSlashPolicy(keccak256(abi.encodePacked(uint256(proofType)))) returns an empty (disabled) policy for every proof type 0 to 10.
  • deploy/protocol/mainnet-protocol.config.json has no slash policy section.
  • With a disabled policy, _proposeSlash reverts with SlashReasonDisabled (SlashingManager.sol:629, 724). Nodes log Slash policy is disabled; excluding the faulted member from local E3 work and only exclude the member (crates/evm/src/slashing_writing/handlers.rs:136-150).

Question

Is this the intended launch state? If so, please record the plan for enabling policies. If not, the deployment needs a governance transaction that sets the Lane A policies.

PR #2010 adds a dated note to the operator docs.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contractsRelated to the enclave-contracts packagequestionFurther information is requestedsecurityRelevant to security

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions