Belong is building the world’s first performance-based affiliate network for physical businesses, combining real-world experiences with on-chain technology to transform how venues, promoters, and customers interact.
Live
Triaged by Immunefi
Step-by-step PoC Required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Build Commands, Test Commands, and How to Run Them
https://github.com/belongnet/checkin-contracts/tree/main/docs/guides
Asset Accuracy Assurance
Bugs found on assets incorrectly listed in-scope are valid.
Code Freeze Assurance
Code of the assets in scope is frozen while the program is live.
Duplicate submissions of bugs are valid. Duplicate submissions of Insights are invalid.
The project commits to keeping private all info related to bug findings until this program is over. This means the project will not leak info about any bug findings or planned bug fixes, including bug findings found independently by the project or from concurrent private audits.
Previous Audits
Belong’s completed audit reports can be found at https://hacken.io/audits/belong-net/. Unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Private Known Issues Reward Policy
Private known issues, meaning known issues that were not publicly disclosed, are valid for a reward.
Where might Security Researchers confuse out-of-scope code to be in-scope?
Smart contracts only from ./contracts/v2 should be audited. LONG.sol has been built by OZ Wizard.
Is this an upgrade of an existing system? If so, which? And what are the main differences?
Factory has been updated from the previous version, which stored token and royalties receiver codes within itself. Currently, Factory utilises a minimal proxy clone deployment.
What ERC20 / ERC721 / ERC777 / ERC1155 token standards are supported?
- LONG.sol - ERC20
- CreditToken.sol - ERC1155
- AccessToken.sol - ERC721
Which chains and/or networks will the code in scope be deployed to?
BNB Smart Chain
What external dependencies are there?
- Solady library.
- Uniswap/Pancakeswap V3.
What are the most valuable educational resources already available? (Ie. Documentation, Explainer videos or articles, etc)
Documentation can be found in: ./docs/ folder.
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
Permanent freezing of funds
Permanent freezing of NFTs
Unauthorized minting of NFTs
Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
Protocol insolvency
Permanent freezing of unclaimed royalties
Permanent freezing of unclaimed yield
Theft of unclaimed royalties
Theft of unclaimed yield
Temporary freezing of funds for at least 24 hour
Out of scope
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers