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

The on-chain instance of iGain v2 would be expired and redeployed continuously. Therefore, it’s difficult to  choose a specific term on blockchain explorer for reference, but we put the previous expired contracts as an example.

Hakka Finance is a set of decentralized finance (DeFi) applications, which form an all-inclusive ecosystem of tools that allow users to pursue financial sovereignty. The current product offering consists of a stablecoin automated market maker (AMM) DEX, a gamified insurance product, an onchain prediction market and a derivative framework.

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Temporary freezing of funds for more than 24 hrs

Spoofing content on the target application (Persistent)

Users Confidential information disclosure such as Email

Subdomain Takeover without financial loss (applicable for subdomains with no addresses published)

Privilege escalation to access unauthorized functionalities

Smart contract unable to operate due to lack of funds

Block stuffing for profit

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

Theft of gas

Unbounded gas consumption

Any governance voting result manipulation

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

Permanent freezing of funds

Miner-extractable value (MEV)

Protocol insolvency

Ability to execute system commands

Extract Sensitive data/files from the server such as /etc/passwd

Stealing User Cookies

Bypassing Authentication

Taking down the application/website

Signing transactions for other users

Redirection of user deposits and withdrawals

Subdomain takeover resulting in financial loss (applicable for subdomains with addresses published)

Wallet interaction modification resulting in financial loss

Direct theft of user funds

Submitting malicious transactions to an already-connected wallet

Tampering with transactions submitted to the user’s wallet

Hakka Finance Smart Contracts

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team.

The following vulnerabilities are not eligible for a reward:

  - In [https://github.com/artistic709/ImpermanentGain/blob/main/v2/IGainBase.sol](https://github.com/artistic709/ImpermanentGain/blob/main/v2/IGainBase.sol), on line 701, the transaction will fail if *reserveOut* is smaller than *amountIn*. This happens when you want to sell Long or Short with *burnA()* or *burnB()* and the liquidity is too small compared to the amount to be sold.

Payouts are handled by the __Hakka Finance__ team directly and are denominated in USD. However, payouts are done in __USDT__, __USDC and ETH__, with the choice of the ratio at the discretion of the team.

Title	Description	Link
Hakka Finance Smart Contracts	Program Smart Contracts
Hakka Finance Smart Contracts	Program Smart Contracts
Hakka Finance Smart Contracts	Program Smart Contracts
Hakka Finance Smart Contracts	Program Smart Contracts

Hakka Finance

Codebase