Gala Games
The decentralized Gala Games entertainment ecosystem uses web3 to allow user ownership of tokens and in-game items. Because cryptocurrency wallets and digital asset ownership are part of the Gala Games experience, security is of utmost importance.
PoC required
KYC required
Rewards by Threat Level
Rewards are distributed according to the impact the vulnerability could otherwise cause based on the Impacts in Scope table further below.
Restrictions on Security Researcher Eligibility
Security researchers who fall under any of the following are ineligible for a reward:
- KYC blocked security researchers - Gala Games cannot pay bounties to individuals that take part in criminal or illegal activities. Therefore, Gala Games must perform KYC and wallet verification due to rules & regulations.
- KYT blocked wallets - the identity of the individual must be verified as well as the legitimacy of the wallet on which they would like to receive their bounty payment due to rules & regulations.
Proof of Concept (PoC) Requirements
A PoC is required for the following severity levels:
- Smart contract, Critical severity
- Smart contract, High severity
- Smart contract, Medium severity
- Websites & applications, Critical severity
- Websites & applications, High severity
- Websites & applications, Medium severity
All PoCs submitted must comply with the Immunefi-wide PoC Guidelines and Rules. Bug report submissions without a PoC when a PoC is required will not be provided with a reward.
Reward Payment Terms
Payouts are handled by the Gala Games team directly and are denominated in USD. However, payments are done in $GALA.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability. For avoidance of doubt, if the reward amount is USD 5 000 and the average price is USD 1.75 per token, then the reward will be 2857.142857 units of that token.
Program Overview
The decentralized Gala Games entertainment ecosystem uses web3 to allow user ownership of tokens and in-game items. Because cryptocurrency wallets and digital asset ownership are part of the Gala Games experience, security is of utmost importance.
For more information about Gala Games entertainment ecosystem, please visit https://gala.com/.
Gala Games provides bounty rewards in $GALA. For more details about the payment process, please view the Rewards by Threat Level section further below.
KYC Requirement
The provision of KYC and KYT is required to receive a reward for this bug bounty program, where the following information will be required to be provided:
- Identity Proof (Passport, / National ID).
- Legitimacy of the wallet on which they would like to receive their bounty payment.
KYC and KYT information is only required on confirmation of the validity of a bug report and is mandatory to be eligible for a bug bounty payout.
Responsible Publication
Gala Games adheres to category 3. This Policy determines what information whitehats are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Gala Games adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms stated in this page.
KYC required
The submission of KYC information is a requirement 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.