Pantos is a multichain token system, enabling tokens to exist on multiple blockchains and be freely transferable, thus unlocking the real superpowers of digital assets and making them technology-agnostic.


Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Theft of unclaimed royalties

Permanent freezing of unclaimed yield

Permanent freezing of unclaimed royalties

Temporary freezing of funds

Smart contract unable to operate due to lack of token funds

Block stuffing

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

Theft of gas

Execute arbitrary system commands

Direct theft of user funds

Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions

Subdomain takeover without already-connected wallet interaction

Source Code

Gitbook

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 200K. 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 50K is to be rewarded in order to incentivize security researchers against withholding a critical bug report.

- For critical smart contract bugs on testnet assets, the reward is paid as a flat amount of 50K. This is because there are no actual funds at risk on the testnet, hence limits objective calculation. 

- For critical web/apps bug reports will be rewarded with 50K, only if the impact leads to:
    - A loss of funds involving an attack that does not require any user action
    - Private key or private key generation leakage leading to unauthorized access to user funds 

All other impacts that would be classified as Critical would be rewarded a flat amount of 20K. The rest of the severity levels are paid out according to the Impact in Scope table.

__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 200K to 10K 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.

Pantos

Codebase

Documentation