Ante Finance
Ante Finance enables blockchain protocols and developers to create incentivized, real-time, and autonomous guarantees for any smart contract system on any blockchain. Ante envisions becoming the global Schelling point for decentralized trust.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Insolvency
Loss of funds in Ante Pool that is not triggered by a valid withdrawal of funds by the user who deposited or settlement (in the case of a failed Ante Test)
Inability for stakers or challengers to withdraw funds from the pool (except in the case of a failed Ante Test)
AntePool triggers test failure workflow when underlying AnteTest did not revert or fail
Theft of unclaimed yield
Permanent freezing of unclaimed yield
Incorrect payment to stakers from challenger decay mechanism (aside from inaccuracy described above)
Incorrect loss of funds from challengers due to challenger decay mechanism (aside from inaccuracy described above)
Incorrect payout to challengers on settlement following a failed Ante Test
Withdrawal of staked funds by stakers without waiting for 24 hr window to pass following initialization of unstake
Out of scope
- Best practice critiquesAttacks that are already known or outlined in any audits, https://github.com/antefinance/ante-v05-core/tree/v0.5/audit
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