Skip to content

Slashing Policy

Slashing in the Forta Network

Both Node Runners and Detection Bots are required to stake FORT tokens in order to participate in the Forta Network and earn FORT rewards. Soon, delegated staking will allow other Forta community members to stake tokens on node operations. Staking aligns incentives amongst Network participants and also acts as a sybil resistance mechanism. As a further security feature, Network participants also risk their staked FORT being slashed as follows:

  • Slashing Node Runners. Although the Forta work assignment algorithm takes into account SLA performance and node runners that fail to execute their assigned work correctly should be organically pushed out of the Network over time, for additional reliability, Node Runners are also subject to slashing if they fail to execute their assigned work correctly outside of the SLA factors or if they attempt misconduct.

  • Slashing Detection Bots. Although Detection Bots are deployed via docker containers and must meet specific technical criteria in order to be assigned by the Forta work assignment algorithm, for additional reliability, Detection Bots are also subject to slashing if they fail to meet Detection Bot guidelines or negatively impact the Network, or attempt malicious behavior.

Purpose of this Slashing Policy

In FP-2, FORT token holders approved the implementation of slashing architecture to further secure the Network, which includes the endowment of two protocol roles to one or more multisigs that have the power to determine the outcome of technical complaints in the Network:

  1. Arbiter Multisig(s) - responsible for receiving, reviewing and resolving the outcome of complaints (in the form of Slashing Proposals) in the Forta Network
  2. Slasher Multisig(s) - responsible for approving and executing validated Slashing Proposals

Since certain parts of the slashing architecture are not yet expressed in smart contract code running on-chain, the purpose of this Slashing Policy is to establish norms that guide the actions of multisig signors beyond what is currently expressed on-chain. This policy presumes that any signor that does not comply with the norms laid out in this Slashing Policy will be replaced via decentralized governance.

The substance of this policy is intended to ensure that the Forta slashing architecture supports a healthy and robust Network where participants perform their work correctly, while minimizing the risk to honest participants of being economically penalized while interacting with the Forta Network in good faith.

Forta Slashing Process

The entire Forta slashing process takes place on Polygon mainnet. If you need to bridge your FORT tokens from Ethereum to Polygon, check out this guide. Please carefully review the Technical Slashing Guidance provided at the bottom of this page to submit a final Slashing Proposal.


Any Proposer can submit an on-chain Slashing Proposal by following the Technical Slashing Guidance, which requires:

  • the Proposer providing sufficient evidence substantiating the complaint against the Slashing Subject; and
  • the Proposer making a 1000 FORT token deposit.

The Proposer’s 1000 FORT deposit is at risk of being slashed if the Arbiter determines the Slashing Proposal does not conform to the requirements herein, or it is deemed malicious. Therefore, the Proposer must take care to submit sufficient verifiable evidence (e.g. screen captures, log files, or any other file that proves the accusations) in accordance with the formatting and file limitations set out in the Technical Slashing Guidance. Such evidence must remain publicly accessible through the entire slashing process.

If a Slashing Proposal is ultimately validated and executed, the FORT tokens of the Slashing Subject (which could include anyone who has delegated stake to such Slashing Subject) targeted by the Slashing Proposal will be slashed and distributed as follows:

  • 80% of slashed stake will go to the Proposer
  • 20% of slashed stake will be returned to a community treasury at 0xC99884BE6eEE5533Be08152C40DF0464B3FAE877 on Polygon


The Arbiter is a protocol role responsible for receiving, reviewing and resolving technical complaints in the Forta Network. Following review of each Slashing Proposal, one of three possible outcomes will be determined by the Arbiter:

  1. Withdrawn Slashing Proposal - no parties are penalized
  2. Slashing Proposal is withdrawn from the slashing process by the Arbiter following review
  3. 1000 FORT token deposit returned to Proposer; no stake slashed from Slashing Subject
  4. e.g. Arbiter review surfaces additional evidence that renders Slashing Proposal complaint moot, or parties mutually agree to alternative resolution or withdraw complaint

  5. Denied Slashing Proposal: Proposer is penalized

  6. Slashing Proposal is denied as eligible by the Arbiter following review
  7. 1000 FORT token deposit of Proposer is slashed to community treasury
  8. e.g. Arbiter review determines Slashing Proposal was made in bad faith or did not contain accurate or sufficient evidence proving misconduct

  9. Validated Slashing Proposal - Slashing Subject is penalized

  10. Slashing Proposal is validated as eligible for slashing by the Arbiter following review and is classified as an “Operational” or “Misconduct” complaint as set out below
  11. 1000 FORT token deposit returned to Proposer
  12. e.g. Arbiter review determines Slashing Proposal was made in good faith and evidence is sufficient for Arbiter to determine outcome

Following receipt of a Slashing Proposal, the Arbiter shall make best efforts to determine the outcome of a Slashing Proposal within 10 days. All activity undertaken by the Arbiter pursuant to this policy will be published in the Discord channel #slashing-proposals in advance of being executed on-chain, subject to redaction only where necessary to protect the security or integrity of the Forta Network. This disclosure should include the determination made by the Arbiter accompanied by the reasoning for reaching such a determination.


The Arbiter address will confirm any Validated Slashing Proposal as either an “Operational” or “Misconduct” complaint, with the following consequences:

  1. Misconduct Complaint - Slashing Subject at risk of up to 90% slash (if executed by Slasher Multisig). For example:

  2. Censoring, forging or tampering with bots alerts

  3. Forging or failing to provide performance metrics
  4. Bot is part of an attack against Network or its participants
  5. Any other evidenced misconduct in the Network
  6. Bots whose alert misrepresents the purpose stated on their description or that fail to alert subscribers in the way they advertise
  7. Any other evidenced operational failures in the Network

  8. Operational Complaint - Slashing Subject at risk of up to 15% slash (if executed by Slasher Multisig). For example:

  9. Scan Node Slashing Subject:

    • Failure to run a Node with the minimum technical requirements set out in the Forta Docs
    • Failure to run a Node at expected quality standards not captured by the SLA calculation
  10. Detection Bot Slashing Subject:

    • Bots that clog the network (spam)
    • Bots that inappropriately affect Scanner Node SLAs
    • Bots that demand an excessive amount of resources from Scanner Nodes


Following review and resolution of a Validated Slashing Proposal by the Arbiter as either “Operational” or “Misconduct”, a Proposal will be delivered to the following Ethereum addresses for final review and, if thought appropriate, execution of a Slashing Proposal:

Misconduct Complaints - the Forta Governance Council Multisig

Operational Complaints - the Arbiter Multisig

If the Arbiter alters the original classification of a Slashing Proposal from Malicious to Operational or vice-versa, it must provide evidence justifying such alteration on-chain and in Discord.

Arbiter Multisig Delegation

Initially, the Arbiter role will be delegated by the Forta Governance Council to a 2-of-3 Gnosis Safe multisig dubbed the Community Arbitration Committee (the “CAC”). The CAC will determine if each Slashing Proposal is complete and being made in good faith, by investigating the evidence submitted and following up with stakeholders as necessary. Following review, the CAC will publish its determination and reasoning in the #slashing-proposals Discord channel and thereafter execute such decisions on-chain.

The initial members of the CAC include (Discord usernames, as found in #slashing-proposals):

  • ba3is#1622
  • slanders#4806
  • 0xRoberto#8830

If members of the CAC do not stay aligned with the community and resolve disputes appropriately, the Forta community may lobby the Council to remove or replace a member, through an FPP proposal or directly.

Conflicts of Interest. Slashing Proposals could pose a conflict of interest due to a member of the CAC’s activities in the Forta Network. If any CAC member believes that they are conflicted with respect to a Slashing Proposal, they must disclose such conflict.

Compensation. Each member of the CAC shall receive 160 FORT for each Slashing Proposal reviewed and processed, paid by the Network monthly.

Liability. The only recourse for the CAC not fulfilling their duties under this Slashing Policy is to be replaced via the Forta community governance process. The CAC has no legal or fiduciary responsibility to any stakeholder in the Forta Network and cannot be held responsible for any consequence that arises from Network participant behavior or any economic penalties incurred by stakeholders involved with the slashing process.


All data related to staking and slashing in the Forta Network is publicly available on the Polygon network for review. In addition, all activity undertaken by the Arbiter pursuant to this policy will be published in the Discord channel #slashing-proposals in advance of being executed on-chain, subject to redaction only where necessary to protect the security or integrity of the Forta Network. This disclosure should include posting what decisions and classifications were made and a summary of the reasoning. Any Slashing Proposal decided upon by the Council will be published in Council minutes according to the Council Bylaws.

Illustrated process