HaloDAO

HaloDAO is driving liquidity to regional, asset backed stablecoins by building a stablecoin optimized AMM and stablecoin focused Lending Market and linkages with existing wallets and exchanges around the world. With a greater supply of region specific stablecoins, users will be able to access the permissionless Decentralised Finance (DeFi) economy, thereby lowering the barrier to individual financial participation in a region of the world with a high potential of growth and impact.

For more information about HaloDAO, please visit their website at https://www.halodao.com/.

This bug bounty program is focused on their smart contracts, website, and application, and is focused on preventing the following impacts:

• Freezing of contract’s holdings
• Theft of yield
• Token holders temporarily unable to transfer holdings
• Transient consensus failures
• Smart contract drainage
• Smart contract failed to return promised returns
• Contract consumers unbounded gas
• Block stuffing
• Gas griefing
• Griefing denial of service
• Cryptographic flaws
• Leak of user data
• Deletion of user data
• Site goes down
• Accessing sensitive pages without authorization
• Users spoofing other users
• UI level bugs
• Math formula discrepancies

Rewards are distributed according to the following vulnerability classification system:

Rewards for web/app vulnerabilities are distributed according to the Immunefi Vulnerability Severity Classification. Please refer to the portion under prioritized vulnerabilities to check the web/app vulnerabilities that are covered in the scope for rewards.

All web/app bug reports must come with a PoC in order to be considered for a reward. Additionally, all Medium, High, and Critical Smart Contract bug reports must come with a PoC.

Critical web/app and smart contract bug reports are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also taking into consideration branding and PR aspects, at the discretion of the team. However, for smart contract vulnerabilities, the reward is a minimum of USD 50 000.

The final reward amount for other severity levels will be determined by HaloDAO on a case-by-case basis. By submitting a bug report, you agree that HaloDAO has the final decision on the amount to be rewarded.

The final reward amount for other severity levels will be determined by HaloDAO on a case-by-case basis. By submitting a bug report, you agree that HaloDAO has the final decision on the amount to be rewarded.

Payouts are handled by the HaloDAO team directly and are denominated in USD. Payouts are only done in RNBW.

For additional reference, the HaloDAO GitHub can be found at https://github.com/HaloDAO/. However, only the assets listed as in-scope in this table are considered covered under the bug bounty program.

AmmRewards.sol () can be found as halo-rewards-v1/AmmRewards.sol at master · HaloDAO/halo-rewards-v1 and rHalohalo.sol() can be found as halo-rewards-v1/Halohalo.sol at master HaloDAO/halo-rewards-v1.

Only bugs that directly affect the web/app items listed in the Assets in Scope table are considered as in-scope of the bug bounty program. All others are out-of-scope.

Impacts in Scope

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.

Smart Contracts

• Freezing of contract’s holdings
• Theft of yield
• Token holders temporarily unable to transfer holdings
• Transient consensus failures
• Smart contract drainage
• Smart contract failed to return promised returns
• Contract consumers unbounded gas
• Block stuffing
• Gas griefing
• Gas griefing
• Griefing denial of service
• Cryptographic flaws

Web/App

• Site goes down
• Users spoofing other users
• UI level bugs
• Math formula discrepancies

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks
• Reports about outdated dependencies
• Reports about vulnerabilities in dependencies, when those vulnerabilities do not impact Solido’s use of the dependency

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by this bug bounty program:

• Testing on Mainnet HaloDAO is not allowed, all testing should be done on private testnets only.
• Test must not violate any law or compromise any data that doesn’t belong to users.
• Public disclosure of a bug, exploit, or vulnerability is strictly prohibited.
• Using vulnerability testing tools that generate significant volumes of traffic, may disqualify you from getting a reward.
• Social engineering, phishing, or physical attacks against HaloDAO employees, users, or the network infrastructure is not allowed.
• Submission of issues will follow a first-come-first-serve basis. Duplicate issues are not eligible for a reward.
• Determinations of eligibility and all terms related to an award are at the final discretion of the HaloDAO team.
• Please read our Disclosure Policy. Submissions that do not adhere to the disclosure policy will not be eligible for a reward.