Blockian

LonelySloth

yttriumzz

Paludo0x

Stormy

https://drive.google.com/file/d/1DomEnIQ0o4Fv7ELFvnVAIP9vgd6Ez__A/view?usp=sharing

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

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

Permanent freezing of funds

Permanent freezing of NFTs

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for more than 3 hours

Temporary freezing of NFTs for more than 3 hours

**Proof of Concept (PoC) Requirements**

A PoC, demonstrating the bug's impact, is required for this program and has to comply with the [Immunefi PoC Guidelines and Rules](https://immunefisupport.zendesk.com/hc/en-us/articles/9946217628561-Proof-of-Concept-PoC-Guidelines-and-Rules).

**Eligibility Criteria**

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- On OFACs SDN list 
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project 
- Security auditors that directly or indirectly participated in the audit review

**Responsible Publication**

Whitehats may not publish their bug reports from this program.

However Immunefi will publish a leaderboard and high-level summary of the results of this program which whitehats can use for their portfolio.

**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.

**Immunefi Standard Badge**

By adhering to Immunefi’s best practice recommendations, Hinkal has satisfied the requirements for the [Immunefi Standard Badge](https://immunefisupport.zendesk.com/hc/en-us/articles/15006865432209-The-Immunefi-Standard-Badge).

The following reward terms are a summary, for the full details read our [Hinkal Invite Only Program Reward Distribution Terms](https://immunefisupport.zendesk.com/hc/en-us/articles/24006220866065-Hinkal-Invite-Only-Program-Reward-Distribution-Terms). 

Each participating whitehat will receive a guaranteed reward $2,500

On top of this, there are additional rewards per-unique-bug found:
- $2,500 per Critical
- $1,500 per High

For this Invite Only Program, duplicates and private known issues are valid for a reward.

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 Payment Terms**

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

Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.

NAME	EARNINGS	TOTAL VALID BUGS	HIGH
1 Blockian	$4,000	1	1
2 LonelySloth	$2,500	0	0
3 yttriumzz	$2,500	0	0
4 Paludo0x	$2,500	0	0
5 Stormy	$2,500	0	0

IOP | Hinkal

Status