GeroWallet
GeroWallet is an all-in-one DeFi app designed to be a powerful instrument for experienced and new users alike. GeroWallet delivers a redefined UX by focusing on a user-centric design. Our product features a built-in multi-functional toolkit that boasts swapping, liquidity lock, staking, dAPP connector and fiat on/off ramp functionality.
PoC required
Rewards by Threat Level
Rewards are distributed for critical vulnerabilities only, defined as vulnerabilities that lead directly to a financial loss for users.
All bug reports must come with a PoC demonstrating direct financial impact in order to be accepted.
Bug reports that do not contain a vulnerability that leads to a direct loss of funds are not accepted in this bug bounty program. Additionally, any vulnerability that involves social engineering is not in-scope.
Payouts are handled by the GeroWallet team directly and are denominated in USD. Payouts are done in $GERO.
Program Overview
GeroWallet is an all-in-one DeFi app designed to be a powerful instrument for experienced and new users alike. GeroWallet delivers a redefined UX by focusing on a user-centric design. Our product features a built-in multi-functional toolkit that boasts swapping, liquidity lock, staking, dAPP connector and fiat on/off ramp functionality.
For more information about GeroWallet, please visit https://gerowallet.io/.
The bug bounty program covers its Website, Mobile Application and Chrome Extension and is focused on preventing the following impacts:
- Thefts and freezing of principal of any amount
- Theft of any funds / tokens / nfts
- Leak of seed phrase
- Manipulating the user to send funds within the wallet
- Man in the middle attacks that lead to financial loss
- XSS/CSRF with financial loss as a result
- Loss of any fiat amount when user will be using on/off ramp services
KYC not required
No KYC information is required for payout processing.
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- Any testing with pricing oracles or third-party smart contracts
- Attempting phishing or other social engineering attacks against our employees and/or customers
- Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
- Any denial of service attacks that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
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 which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.