Forta Network

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target.

If an impact can be caused to any other asset managed by Forta that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical and High impacts.

Exceptions: The are specific bugs not eligible for a Bounty, as they have already been identified and fixes are in progress.

• A protocol vulnerability where a Scan Pool Owner is able to withdraw their stake without disabling their scan nodes if there is enough Delegated Stake in the Scan Pool. The intention was to always require Owners to have a minimum stake level so that they always have a direct incentive to avoid malicious activity.
  The Delegator’s stake should be unallocated when owner’s stake is withdrawn Add check to disableScanner before decrementing the amount of enabled scanners in a scanner pool Bypassing of max allocation by staking very large amount (needs to be further clarified)
• Issue in setting up a new pool with large stake setDelegationParams function in RewardsDistributor not setting delegationParamsEpochDelay
• Setting a pool's fee to 0 causes the pool's fee to actually become 100% because the contract assumes that trying to set it to 0 means there is no fee set, and thus defaults to 100%.
• Signing up for subscriptions repeatedly and hitting verify email a lot which sends a lot of emails
• Bots that emit too many alerts
• An owner can emit infinite bots, and too many is too many - but staking mitigates that and we can slash + take other actions
• Nodes that handle their nodes insecurely - putting them on the public internet / exposing sensitive credentials within network endpoints
• Someone with a private key of an enabled&staked scan node can submit fake alerts for any bot