All code of Pragma can be found at [https://github.com/Astraly-Labs/pragma-oracle](https://github.com/Astraly-Labs/pragma-oracle)
and [https://github.com/Astraly-Labs/pragma. ](https://github.com/Astraly-Labs/pragma)Documentation for the assets provided in the table can be found at [docs.pragma.build](https://docs.pragma.build/)

Pragma is the leading Oracle on StarkNet, recognised for providing the most reliable data feeds to its ecosystem. This network relies on three types of data sources: First Party, Third Party, and On-chain data.

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results.

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

Permanent freezing of funds

Allow unauthorized actors to manipulate/publish any data entry

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

Theft of gas

Unbounded gas consumption

Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below. 

__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 50 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 bug report.   

__Repeatable Attack Limitations__

In cases of repeatable attacks for smart contract bugs, only the first attack will be counted, regardless of whether the smart contract is upgradable, pausable, or killable.

__Proof of Concept (PoC) Requirements__

A PoC is required for the following severity levels:
- Smart Contract + Critical + PoC Required
- Smart Contract + High + PoC Required
- Smart Contract + Medium + PoC Required

All PoCs submitted must comply with the Immunefi-wide [PoC Guidelines and Rules.](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules) Bug report submissions without a PoC when a PoC is required will not be provided with a reward.

__Feasibility Limitations__

The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.

Therefore, Immunefi has developed a set of [feasibility limitation standards](https://immunefisupport.zendesk.com/hc/en-us/articles/16913132495377-Feasibility-Limitation-Standards) which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

__Public Disclosure of Known Issues__

Bug reports covering previously-discovered bugs acknowledged below are not eligible for any reward through the bug bounty program. 
- [https://github.com/NethermindEth/PublicAuditReports/blob/main/NM0147-FINAL_PRAGMA.pdf](https://github.com/NethermindEth/PublicAuditReports/blob/main/NM0147-FINAL_PRAGMA.pdf)

__Reward Payment Terms__

Payouts are handled by the Pragma team directly and are denominated in USD. However, payments are done in USDC.

Pragma Oracle

Resources & Documentation