All smart contracts of Msgport can be found at [https://github.com/msgport/](https://github.com/msgport/). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts found in contracts which are deployed to multiple chains will be treated as one singular issue.

Documentation and further resources can be found here:

  - [https://docs.msgport.xyz/](https://docs.msgport.xyz/)
  - [https://docs.msgport.xyz/learn/messaging-protocols/ormp/#message-flow-design](https://docs.msgport.xyz/learn/messaging-protocols/ormp/#message-flow-design)

If an impact can be caused to any other asset managed by Msgport 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. The vulnerability will then be evaluated by Msgport in good faith to determine where it would lie on the vulnerability scale.

RingDAO refers to the next governance version of Darwinia Network. Darwinia Chain, Msgport and XAPI are governed by RingDAO.

Exploits resulting in the permanent locking, loss, or theft of user funds

Permanent DoS attacks (excluding volumetric attacks)

Attacker ability to set or modify Darwinia Msgport default settings for another UA

Any governance voting result manipulation

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Contract fails to deliver promised returns, but doesn't lose value

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

All message delivery failures due to UA errors, including the “outOfGas” error, which result in permanent locking, loss, or theft of user funds are not accepted within this bug bounty program.

Rewards are distributed according to the impact of the vulnerability based on the Immunefi [Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 

__Reward Calculation for Critical Level Reports__

For critical smart contract bugs, the reward amount is __10%__ of the funds directly affected up to a maximum of __USD 10 000__. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of __USD 5 000__ is to be rewarded in order to incentivize security researchers against withholding a critical bug report.

__Repeatable Attack Limitations__

  - If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk. 

  - For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward. 

__Reward Calculation for High Level Reports__

  - High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of __USD 3 000 to USD 5 000__ depending on the funds at risk, capped at the maximum high reward.  

  - In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.

__Reward Payment Terms__

Payouts are handled by the __Itering__ team directly and are denominated in __USD__. However, payments are done in __USDC__ on Arbitrum (Prefered) or Ethereum.

RingDAO

Resources & Documentation