Trader Joe

Impacts only apply to assets in active use by the project like contracts on mainnet or web/app assets used in production. Any impact that applies to assets not in active use, like test or mock files, are out-of-scope of the bug bounty program unless explicitly mentioned as in-scope.

Smart Contracts

• Smart Contracts - PoC, Smart Contract bug reports are to include a runnable Proof of Concept (PoC) in order to prove impact.
• For more information on PoCs please visit: Proof of Concept (PoC) Guidelines and Rules
• All smart contracts of Trader Joe can be found at: https://github.com/traderjoe-xyz/joe-v2

Whitehats are highly encouraged to review any potential subdomains and what specific port(s) are in scope. Even though the domain may be the same, different ports may point to different assets.

Dev Environment and Documentation

Trader Joe has included dev documentation and/or instructions to help in reviewing code and exploring for bugs:

• https://docs.traderjoexyz.com/
• https://github.com/traderjoe-xyz/joe-v2

Impacts to other assets

Hackers are encouraged to submit issues outside of the outlined Impacts and Assets in Scope.

If whitehats can demonstrate a critical impact on code in production for an asset not in scope, Trader Joe encourages you to submit your bug report using the “primacy of impact exception” asset.

Impacts in Scope

(For Blockchain/DLT and Smart Contracts Only) This program is considered to be governed by Primacy of Impact. For more information on what this means visit: Best Practice - Primacy of Impact vs Primacy of Rules.

Impacts are based on the Immunefi Vulnerability Severity Classification System V2.2.

At Immunefi, we classify bugs on a simplified 5-level scale:

• Critical
• High
• Medium
• Low
• None