Badger DAO (BADGER): tokenomics, risks and score
A protocol building yield strategies for tokenised Bitcoin on Ethereum, which suffered a front end compromise that drained user funds.
What Badger DAO is, and what it does
This is a DeFi protocol. It provides a financial service such as trading, lending or derivatives through smart contracts rather than through a company, so there is no account to open and no one to approve you.
What the BADGER token itself does: It receives a share of the fees the protocol collects, so holding it is a claim on real revenue.
Where it runs: Multi chain. Mechanism: Bitcoin yield strategies on Ethereum. It has been running since 2020, so roughly 6 years.
The facts
- TICKER
- BADGER
- SECTOR
- DeFi
- CHAIN
- Multi chain
- LAUNCHED
- 2020, so around 6 years of operating history
- MECHANISM
- Bitcoin yield strategies on Ethereum
- MAXIMUM SUPPLY
- 21 million
- VALUE CAPTURE
- Fee share
- UPGRADE CONTROL
- DAO governed
- VESTING
- Complete
- LIQUIDITY BAND
- Micro cap. Thin, often a single venue or pool. Treat the quoted price as indicative only.
How the score breaks down
Each dimension is explained on the directory page, and the reasoning behind it is taught in the Academy research process.
Supply and value capture
A hard maximum supply that cannot be raised without the agreement of essentially every participant. A share of protocol fees reaches holders directly, which is the strongest form of value capture available.
Changes go through token holder governance, so control is distributed but influenced by whoever holds most. Ownership is moderately concentrated. A handful of large holders could move the market.
Where it is strong and where it is not
- Has operated for around 6 years and through at least one full bear market
- Supply is capped, so holders are not diluted indefinitely
- The token captures real protocol revenue rather than relying on speculation alone
- Audited, with published reports
- Thin liquidity. Check order book depth before assuming you can exit
- Has 1 recorded incident on its history
Incident history
An attacker injected malicious code into the front end through compromised infrastructure, tricking users into signing approvals that drained roughly 120 million dollars. The contracts themselves were not at fault.
Our read
The main risk
A front end compromise drained user funds despite sound contracts, and the protocol never fully recovered.
Before you buy anything
Check the contract address against the project's own documentation rather than a search result or a screener link, since impersonation tokens with identical names and logos are listed constantly. Check the order book depth before assuming you can exit at the quoted price. And write down what would make you wrong before you buy, not after. The Academy thesis module covers why that single habit protects more capital than any indicator.