#104　How the Resolver Works in a Restaking Protocol

## Introduction

In decentralized systems, maintaining security and fairness is crucial to the integrity of the network. One important mechanism that helps achieve this is restaking protocols. Restaking allows validators or participants to add more stake, reinforcing their commitment to the network’s security. However, with more power comes the potential for misuse, and that’s where slashing comes in—a penalty applied to validators for misbehaving, such as double-signing or being offline when they shouldn’t be.

To ensure that slashing is done fairly and only when appropriate, a crucial component known as the resolver plays a key role. The resolver is responsible for reviewing and verifying slashing requests, determining if they are valid, and deciding whether to execute the slash or veto it. This careful decision-making process is essential to avoid unjust penalties and maintain trust in the network.

In this blog, we will dive into the role of the resolver in a restaking protocol, exploring how it interacts with slashing requests and ensures fair outcomes.

## What is Restaking Protocol?

In blockchain networks, particularly those using Proof-of-Stake (PoS) consensus mechanisms, validators are responsible for validating transactions and maintaining the security of the network. Validators typically lock a certain amount of tokens as stake, which acts as a security deposit to ensure they act honestly and in the best interest of the network.

A restaking protocol allows validators to increase their stake by locking additional tokens. This process, called restaking, not only boosts the validator’s stake but also enhances their ability to participate in network activities and secure the blockchain. The more tokens a validator restakes, the higher their chances of being selected to validate transactions and earn rewards. Restaking plays a vital role in reinforcing the trust and security of decentralized systems.

However, with increased power also comes increased responsibility. Validators that behave dishonestly or violate network rules—such as engaging in double-signing (validating conflicting transactions) or experiencing prolonged downtime (failing to participate in block production)—face slashing. Slashing is a penalty mechanism designed to punish these misbehaving validators by reducing their staked tokens or even removing them from the validator pool altogether. This not only deters bad actors but also protects the network from attacks or disruptions.

In the context of restaking, slashing events are triggered when validators violate protocol rules, and this is where the resolver comes in. The resolver is the entity that evaluates whether a slashing proposal is valid, ensuring that penalties are applied fairly and only when necessary. By properly managing slashing and restaking, the protocol can maintain a healthy balance of security and decentralization.

## Introducing the Resolver

The resolver is a critical component in any restaking protocol, functioning as the gatekeeper that evaluates whether slashing penalties should be applied to validators. Its primary role is to make informed decisions based on predefined rules and evidence to ensure that only valid slashing requests are executed.

Unlike the slasher, which acts as the enforcer by applying penalties, the resolver is more akin to a judge. It receives slashing requests, reviews the evidence, and decides whether to proceed with the slash or reject it. This separation of roles ensures that the slashing process is carried out fairly and transparently.

The key responsibilities of the resolver include:

- Evaluating Slash Requests: When a slashing request is submitted, the resolver examines the conditions, checking if the validator in question truly violated the protocol's rules.
- Making Decisions: After evaluating the evidence, the resolver either approves the request, signaling the slasher to penalize the validator, or vetoes it, preventing an unjustified slash.

In short, the resolver ensures that validators are penalized only when they deserve it, maintaining the balance between security and fairness in the protocol.

## The Role of the Resolver in the Slash Process

Here’s how the resolver fits into a typical slash request flow in a restaking protocol:

- Slash Proposal Submitted: A participant (the proposer) submits a request, known as ProposeSlash, to penalize a validator for alleged misbehavior. This could include offenses like double-signing or prolonged downtime.

- Resolver Evaluates the Request: The resolver takes over from here, reviewing the evidence provided in the slash proposal. It checks the validator's behavior, such as their block signatures or activity logs, to determine if an offense has occurred.

- Resolver Decides: Based on its evaluation, the resolver makes a critical decision:
    1. Execute the Slash: If the validator violated the rules, the resolver instructs the slasher to enforce the penalty.
    2. Veto the Slash: If the evidence doesn't support the claim, the resolver vetoes the request, preventing an unjust penalty.

The resolver’s decision-making power is central to the slashing process, ensuring that slashing happens only when the conditions for it are properly met. This avoids unnecessary penalties and builds trust in the protocol.

## How the Resolver Ensures Fairness

The resolver includes several safeguards to ensure that the slashing process is fair, transparent, and verifiable:

- Prevents Malicious or Unjustified Slashing: The resolver plays a key role in preventing abuse. Without it, bad actors could submit false slashing requests, targeting innocent validators. By thoroughly reviewing all evidence, the resolver ensures that only valid requests are processed, protecting validators from unfair penalties.

- Transparency and Verifiability: The resolver's decision-making process is open and auditable. Every decision—whether to slash or veto—is logged on-chain, making the entire process transparent to the community. This promotes trust among validators and participants, as they can verify the fairness of each decision.

By applying these safeguards, the resolver helps protect the protocol from abuse and strengthens the trust between validators, participants, and stakeholders.

## Conclusion

In decentralized protocols, maintaining fairness and preventing abuse is key to sustaining the network’s security and trust. The resolver plays an essential role in this by acting as the decision-making authority in slashing events. It ensures that slashing only occurs when necessary, protecting validators from unjust penalties while safeguarding the network from bad actors.

If you're working on your own decentralized protocol, it’s worth considering how your resolver module is designed. A well-built resolver not only enhances protocol security but also fosters trust and participation from stakeholders. Make sure to think critically about the design, implementation, and transparency of your slashing mechanism to ensure fairness across the board.

## References

- https://docs.restaking.jito.network/
- https://docs.symbiotic.fi/