LooksRare
Submit a BugProgram Overview
LooksRare is the community-first NFT marketplace that actively rewards traders, collectors and creators for participating.LooksRare’s smart contracts are custom-built within a modular system that enables new features to be rolled out over time – without compromising security – thanks to standardized signatures that clearly define the execution scope.
For more information about LooksRare, please visit https://looksrare.org/. This bug bounty program is focused on their smart contracts, website and app, and is focused on preventing:
- Loss of user NFTs
- Loss of user funds
In this program, our focus would be on issues that would result in significant irreversible loss of assets.
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.
All Low, Medium, High and Critical Smart Contract bug reports require a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000.
Payouts are handled by the LooksRare team directly and are denominated in USD. However, payouts are done in LOOKS and ETH, with the choice of the ratio at the discretion of the team.
Smart Contract
- Critical
- Level
- Up to USD $1,000,000
- Payout
- High
- Level
- From USD $5,000
- Payout
- Medium
- Level
- From USD $2,000
- Payout
- Low
- Level
- From USD $1,000
- Payout
Assets in scope
- Smart Contract - LooksRareTokenType
- Smart Contract - LooksRareProtocolType
- Smart Contract - TransferManagerType
- Smart Contract - OrderValidatorV2AType
- Smart Contract - StrategyCollectionOfferType
- Smart Contract - RoyaltyFeeRegistryType
- Smart Contract - RoyaltyFeeSetterType
- Smart Contract - ProtocolFeeRecipientType
- Smart Contract - TradingRewardsDistributorType
- Smart Contract - FeeSharingSystemType
Only those in the Assets in Scope table are considered as in-scope of the bug bounty program. All vulnerabilities found in the https://docs.looksrare.org/ 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 Contract
- Any governance voting result manipulationCriticalImpact
- Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yieldCriticalImpact
- Permanent freezing of fundsCriticalImpact
- Protocol InsolvencyCriticalImpact
- Complete theft of unclaimed yieldHighImpact
- Permanent freezing of unclaimed yieldHighImpact
- Temporary freezing of fundsHighImpact
- Smart contract unable to operate due to lack of token fundsMediumImpact
- Block stuffing for profitMediumImpact
- Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)MediumImpact
- Theft of gasMediumImpact
- Unbounded gas consumption resulting in denial of serviceMediumImpact
- Contract fails to deliver promised returns, but doesn't lose value (not including APRs)LowImpact
Out of Scope & Rules
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)
- Known issues by the project team
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
- Centralization risks
- Sandwich attacks due to insufficient slippage checks
The following activities are prohibited by this bug bounty program:
- Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
- 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
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty