Bug Bounty

The community-driven development approach of GokuMarket rewards the bug bounty hunters for finding bugs in GokuMarket's open-source code. Based on the severity of the bug and the detailed explanation provided, the hunter gets rewarded reasonably and generously. 
Note: these are simply guidelines for the severity of the bugs. Each bug bounty submission will be evaluated on a case by case basis.
Submission
Please email [email protected] with a detailed description of the attack vector. For critical and moderate bugs, we require a proof of concept done on a privately deployed mainnet contract. 
Bug Bounty Payment
Bug bounties will be paid in USDT or GMC, after a DAO vote. The GokuMarketDAO has never refused a bug bounty so far.
Invalid Bug Bounties
The following are out of scope for the bug bounty:
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, admin)
Incorrect data supplied by third party oracles (This does not exclude oracle manipulation/flash loan attacks)
Lack of liquidity
Third party, off-chain bot errors (for instance bugs with an arbitrage bot running on the smart contracts)
Best practice critiques
Sybil attacks
Bug Bounty submission requests opening soon!

TECHNOLOGY - Previous

Security & Audits

Next - About Us

Community Managers

Last modified 1mo ago

Copy link

Contents