BonkDAO is the governance body that spends the treasury of BONK, the community memecoin launched on Solana on Christmas Day 2022. It is worth a directory entry for a reason that has nothing to do with memes: in July 2026 BonkDAO became the clearest worked example of a treasury whose market price was published in its own governance settings. Its quorum was fixed at 1% of token supply, so anyone willing to buy 1% of BONK could pass a proposal alone — and on 6 July 2026 someone spent about $4.4 million doing exactly that and voted roughly $20 million out of the treasury (CoinDesk). No contract was broken. The vote was valid.

An airdrop that became an ecosystem

BONK launched on 25 December 2022 with an initial supply of 100 trillion tokens and no private sale, no venture allocation, and no team round. Half of that supply was airdropped across the Solana community — traders, NFT collectors, artists, developers and contributors — during a period when Solana activity had collapsed in the wake of the FTX failure, which is most of why the token attached itself to the chain's identity so quickly (bonkcoin.com). A share of the launch supply was set aside as a DAO-controlled treasury; that treasury is the thing BonkDAO votes on.

What grew on top of it is unusual for a memecoin. BONK is now the settlement token for a cluster of consumer products — a swap venue, spot and perpetual trading, a Telegram trading bot, and the LetsBonk token launchpad — several of which route a slice of fees into buybacks and burns. Supply has fallen from 100 trillion at launch to roughly 88.0 trillion circulating, with a market capitalisation near $255 million as of 2 August 2026 (CoinGecko). Developer documentation for the ecosystem sits at build.bonkcoin.com.

The gap between that product surface and the DAO's governance surface is the story. BONK acquired an ecosystem, a burn mechanism and, by its own count, over a million holders; its DAO kept the governance configuration of a 2022 community project.

How BonkDAO governs

Proposals are filed as Bonk Improvement Proposals and voted token-weighted on Realms, the standard Solana governance front end built on the SPL Governance program. Realms is a capable framework — it supports councils, multiple vote thresholds, and configurable execution delays — but those protections are per-realm settings, not defaults, and BonkDAO's realm was configured without them.

The three parameters that mattered in July 2026:

• Quorum: 1% of token supply — 879.95 billion BONK. Because BonkDAO's real turnout ran far below that, quorum was not a participation floor at all; it was the whole electorate, and it was purchasable on the open market.
• Voting period: six days, with the proposal visible in public the entire time. Visibility only helps if someone is watching, and roughly 18,000 members were not.
• Execution timelock: none. A passed instruction executed immediately, so there was no window in which the community could have cancelled a transfer it had just noticed (Halborn).

None of these are Realms defects. They are the choices a DAO makes when its governance is set up in a week and never revisited as the treasury grows — which is the general failure pattern catalogued under How DAOs fail.

Every element of that configuration is a per-realm setting rather than a framework default, which is what makes it a design decision the DAO owned. The part that generalises past this one DAO – a participation floor denominated in tokens, guarding a treasury denominated in dollars, with an exchange rate between them that moves without any vote – is treated in general on Quorum and threshold design.

BIP #76: the treasury bought for a fifth of its value

On 30 June 2026 an anonymous wallet filed BIP #76 — "Sowellian BonkDAO", presented as a governance-renewal plan that would install new members and a council and "rebuild the community". Its operative instruction sent 4,426,104,450,305 BONK from the treasury to an address the proposer controlled. Over 4–5 July the same actor bought just over 1% of BONK supply on Bybit and Binance, part-funded by borrowing against DeFi collateral, for roughly $4.4 million — an amount sized to clear the quorum line and little more.

The proposal passed on 6 July 2026 with 882.38 billion BONK in favour against the 879.95 billion threshold, cleared by about 0.3%. Seven wallets voted out of more than 18,000 members — a turnout of about 2.9% — and the buyer held roughly 99.878% of everything cast. With no timelock, execution followed the tally. BonkDAO confirmed the loss publicly, said it had identified the exchange wallets used to accumulate the stake, and began working with exchanges, bridges, the Solana Foundation and law enforcement; at least one exchange suspended BONK transfers while the funds moved (CryptoSlate).

The full technical account — the attack families it belongs to, the defences it defeated, and how it compares with Beanstalk, Steem and Compound Prop 289 — is in DAO security and governance attacks. The participation side of it is treated in Voter apathy and governance participation.

What it changed, and what it didn't

As of August 2026 the reform list circulating around BonkDAO and the wider Solana ecosystem is the expected one: mandatory execution timelocks on treasury instructions, quorum scaled to the value at risk rather than to a fixed share of supply, multisig or council sign-off on large transfers, and anomaly review before execution (crypto.news). These remain proposals rather than shipped configuration, and recovery of the drained tokens is unresolved.

The transferable lesson is narrower than "memecoin DAOs are unserious". BonkDAO's quorum was a number chosen when the treasury was worth little and the token was a joke; it was never re-priced as the treasury grew into eight figures. Any DAO whose quorum is denominated in tokens while its treasury is denominated in dollars has the same exposure, and the exchange rate between the two moves without anyone voting on it. The general treatment of that problem sits under DAO treasury management; the mechanics of the vote itself under Token-weighted voting and Proposal lifecycle.

How Caper approaches this

Caper does not solve governance capture, but it prices it differently, because voting weight on a caper is not a function of tokens held. Each ballot is credited (t·v)/(V·T) — the voter's token balance t multiplied by their vote tokens v, over the vote-token supply V times circulating supply T. Vote tokens are minted one per ballot cast, and a ballot snapshots v before minting the token it earns, so a wallet voting for the first time contributes exactly zero weight to the proposal it is voting on. Buying the token is one factor of two; the other has to be accumulated by turning up, over time, to earlier votes.

Two further details cut against the buy-then-vote shape. The tally credits each ballot min(held_at_vote, live_balance), and anyone may permissionlessly re-clamp that figure downward during a challenge window after voting closes — so stake that arrives for one vote and leaves afterwards loses its credit rather than keeping it. And the pass rule is a share of weight actually cast, not a fixed slice of supply: a proposal carries when its leading option takes 1.5 / option_count of cast weight and that option is not a "no". There is no supply-denominated quorum number to buy, because there is no supply-denominated quorum. Details in Voting and Proposals; the exit path, which pays out at that same weight, in Trading.