Buttonwood is a DeFi project creating and implementing various DeFi protocols, including liquidity aggregation, price-stabilization wrappers, governance, peer-to-peer lending, and risk stratification.
Buttonwood’s approach to innovation focuses on composability—we believe the most useful smart contracts are building blocks, not walled gardens. They should be open-source and as minimal as possible—we seek to build primitives to be used by the entirety of digital finance, not platforms to extract value from the ecosystem. These protocols can be used and incorporated into any other protocol without restriction.
For more information about Buttonwood, please visit https://button.foundation.
This bug bounty program is focused on their smart contracts and website and is focused on preventing the following impacts:
- Thefts and freezing of principal of any amount
- Thefts and freezing of unclaimed yield of any amount
Rewards by Threat Level
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. 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.
Critical smart contract bug reports are further capped at 10% of economic damage, primarily taking into consideration the funds at risk, but also considering other aspects such as PR and branding considerations, at the discretion of the team. However, there is a minimum reward of USD 100 000.
Bug reports of other severity levels will take into consideration the exploitability and impact of the bug reports had they been executed. Buttonwood reserves the right to make the final decision on the reward amount.
Payouts are handled by the Buttonwood team directly and are denominated in USD. However, payouts are done in ETH or USDC, at the discretion of the team.
- Up to USD $500,000
- USD $50,000 - USD $100,000
- USD $10,000 - USD $50,000
Assets in scope
- Smart Contract - BondController.solType
- Smart Contract - UniV3LoanRouter.solType
- Smart Contract - TrancheFactory.solType
- Smart Contract - Tranche.solType
- Smart Contract - BondFactory.solType
- Smart Contract - ButtonToken.solType
- https://github.com/buttonwood-protocol/button-wrappers/blob/main/contracts/oracles/ChainlinkOracle.solTargetSmart Contract - ChainlinkOracle.solType
- TargetSmart Contract - ButtonTokenFactory.solType
- TargetSmart Contract - UnbuttonTokenFactory.solType
- Smart Contract - UnbuttonToken.solType
All code of Buttonwood can be found at https://github.com/buttonwood-protocol. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.
Once deployed on mainnet, the smart contract addresses will be included in this bug bounty program.
Only files in the parent "contracts" folder for both of the assets listed in this table are in 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.
- Loss of user funds staked (principal) by freezing or theftCriticalImpact
- Temporary freezing of fundsHighImpact
- Theft of unclaimed yieldHighImpact
- Freezing of unclaimed yieldHighImpact
- Unable to call smart contractMediumImpact
- Smart contract fails to deliver promised returnsLowImpact
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)
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
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