Beefy (BIFI)

Beefy is a multichain yield optimizer that launched in September 2020 and has been governed since December 2021 by BIFI holders voting on Snapshot. It sits beside Yearn Finance and Convex Finance as one of the surviving first-generation yield aggregators, and its interest for a governance reader is not the vaults but the balance sheet behind them.

Almost every DAO in this directory can pay someone in its own token. Beefy cannot. BIFI's supply is fixed at 80,000 units, the contract has no mint function, and the treasury holds no undistributed allocation to draw down. That single design choice turns every governance decision Beefy makes into a cash decision, and it makes the DAO an unusually clean case study in what a governance organisation actually costs when the bill cannot be paid in inflation.

A DAO with no seigniorage

The BIFI contract is four lines of substance: it mints 80,000 tokens to the treasury on initialisation and exposes no minting permission afterwards. Reading totalSupply() on the mainnet contract returns exactly 80,000 – the figure has not moved and structurally cannot. Beefy's own docs describe this as the point rather than an accident: over 90% of the supply went to the community within two months of the September 2020 launch, and the last founder's-fund emissions expired in July 2022.

The consequence is stated plainly on the same page: because the token was never designed as a payment instrument, Beefy has "a strong preference for any payments to be made in stablecoins, rather than BIFI". Compare that with the compensation model most token-governed DAOs run, where a contributor budget denominated in dollars and settled in the governance token quietly transfers price risk from the treasury to the recipient. Beefy has no such lever. Its operating cost is a cash cost, funded out of revenue, every month.

This also removes a familiar attack surface. A DAO that can mint can dilute; a DAO with a fixed float and a treasury that has already distributed its holdings has nothing to dilute with. The trade is that it must earn what it spends.

Where the money comes from

Beefy's vaults charge a performance fee on each harvest. Those fees are batched on-chain rather than forwarded per-harvest – Beefy found that sending small amounts immediately "depletes that cashflow with a corresponding increase in gas costs" – and the Fee Batch contract then splits the accumulated WETH two ways in a single multicall: part to the incentive programmes that pay BIFI holders, and part swapped to a stablecoin and sent to the treasury.

The holder side is worth reading as a governance design rather than a yield product. Holders can put BIFI in the BIFI Pool and receive WETH, or in the BIFI Vault and have the rewards auto-compounded into more BIFI. Beefy's stated reason for building these is defensive: freely circulating governance tokens, its docs argue, invite both liquidation cascades when they are used as loan collateral and "a parasitic takeover of the project, such as how Convex was able to gain control over Curve". Paying holders to park their tokens in protocol-owned contracts is an explicit answer to the vote-escrow capture problem, reached without locking anyone up.

It also means the fee switch is not hypothetical here. Beefy has run revenue to tokenholders since inception, which puts it on the far side of the argument catalogued under fee switches and value accrual: the question for Beefy governance has never been whether to turn revenue on, only how to divide it.

The payroll vote

Beefy's contributor budget is a recurring, itemised, public proposal – the clearest instance in this directory of a DAO putting its whole wage bill to a vote. BIP:101, passed in July 2026, requests $145,500 per month covering August 2026 to January 2027, broken down as $104,250 for development, $23,750 for business development and $17,500 for marketing and design.

Two things changed with that proposal. The first is the term. Beefy had funded contributors quarterly, and the team argued for a six-month budget on the grounds that quarterly cycles "left contributors with uncertainty over their future and incurs more time each quarter for budget discussions than is desirable" – governance overhead named as a cost and traded away deliberately. The second is that the headline fell $3,000 while the actual spend did not: the reduction is matched by an increase in a service provider's budget in the companion proposal. A reader who tracks only the payroll line would record a cut that did not happen, which is the same reclassification problem that shows up in operating-cost reporting elsewhere.

The proposal is also candid that the budget is a ceiling rather than a forecast: recent months saw "actual payments undershooting the budgeted amount", and the six-month figure is presented as the maximum spend.

Service providers, on renewal

Beefy buys parts of its operating team the way the service-provider model describes: fixed-term engagements that expire and must be re-approved. Staworth Limited was first engaged in January 2025 for financial reporting, non-reserved legal work and general DAO support, and has been renewed on each expiry since – most recently in BIP:102, at $10,000 per month plus 20% VAT, for six months, aligned to the term of the main contributor budget. The renewal proposal makes its own case on delivery: roughly 130 vault strategies shipped in 2026 to that point, about five a week, plus tooling and accounting work.

Other line items renew on the same rhythm – ChainPatrol for brand and phishing takedowns, Octav for accounting data – each as its own proposal with its own vote. The pattern is worth noting because it is rarer than it looks: the engagement has a defined end date, the renewal is a public vote, and the vendor writes a delivery report to win it. Most DAO vendor relationships in this directory renew by silence.

The budget got longer as the room got smaller

The turnout series on Beefy's own funding votes is a clean illustration of governance participation decay, because the proposal type is held constant across two years – it is the same quarterly contributor budget each time:

• 129 voters – BIP:77, Contributor Funding Q2 2024 (April 2024)
• 166 voters – BIP:85, Profit Distribution Framework (December 2024), the series high
• 102 voters – BIP:91, Contributor Funding Q3 2025 (July 2025)
• 44 voters – BIP:97, Contributor Funding Q2 2026 (April 2026)
• 31 voters – BIP:101, Contributor Funding H2 2026 (July 2026)

A 76% fall in voters on the same recurring question, against a space with 11,067 followers. The uncomfortable pairing is that the vote which extended the commitment from three months to six is also the thinnest of the series: the DAO lengthened the term of its largest recurring obligation at the point where the fewest members were watching.

Nothing in the rules catches this. The Beefy space sets its quorum at 1 unit of voting power, so a proposal cannot fail for want of turnout, and the 31 votes on BIP:101 split 2,122 for, zero against – a wide margin on a thin base. That is precisely the configuration the quorum and threshold design page treats as a false safeguard: a threshold set low enough never to bind tells you nothing about whether anyone read the proposal.

When the token traded below the treasury

On 21 April 2026, BIFI's market capitalisation fell below what Beefy's Treasury Council considered the fair value of the assets behind it. BIP:99 asked for, and received, standing authority for the Council to buy BIFI back with treasury assets whenever it trades under that line. It passed with 5,376 voting power for and 152 against, on 76 voters – roughly double the turnout of the payroll votes either side of it.

The proposal's definition of "fair value" is the part worth reading. It is not treasury assets divided by supply. It is what the DAO "could reasonably be expected to receive if it successfully liquidated all of its available treasury assets and settled all of its ongoing payment obligations, divided by the remaining circulating supply" – with treasury-held BIFI removed from both the asset side and the circulating supply, and future payment obligations netted off. The proposal explicitly argues this figure is lower than the naive treasury-divided-by-80,000 number some holders use, which is an unusual direction for a treasury to argue in. It is a discount-to-net-asset-value argument of the kind the token valuation page describes, made by the entity that would benefit from the more flattering version.

What it is not is a redemption right. The buyback is discretionary, exercised by a council on the open market at a price it computes; a holder who wants out sells into whatever bid exists. The distinction between that and a rage-quit right is the difference between the treasury choosing to support a price and a member being able to claim a share.

Who actually holds the votes

Beefy's voting strategy counts BIFI in five places at once: plain BIFI on Ethereum, BIFI held in a Uniswap V3 position on Ethereum, and mooBIFI – the receipt token for a BIFI Vault deposit – on Optimism, Base and Sonic. Delegation sits on top of the whole set.

This is a small design decision with a large effect. Because Beefy pays holders to deposit their BIFI into protocol contracts, a naive balanceOf strategy would have disenfranchised exactly the holders the incentive programme was built to attract, and it would have done so most severely for the most committed ones. Counting the receipt token, on every chain it lives on, is what keeps the token-weighted franchise aligned with the incentive design instead of fighting it – the same activation problem other DAOs solve badly or not at all.

Day-to-day authority is delegated in the ordinary corporate sense rather than the on-chain one. Beefy's docs describe holders as "the legislature" and the core contributor team as "the executive wing", with any Core decision reviewable by a governance vote. There is no on-chain execution path: Snapshot votes are signalling, and the 4-of-7 Treasury Council multisig moves the money.

How Caper approaches this

Beefy's buyback exists because BIFI holders have no way to claim the treasury directly. The token is a claim on a revenue stream and a vote, not on the assets; when the market prices it below those assets, closing the gap requires a council to notice, define a fair value, win a vote and then trade. Every one of those steps is discretionary, and none of them is available to an individual holder who simply wants their share.

Caper takes the other route. A member's claim on the treasury is a method they call themselves, and the share it pays out is the same canonical vote weight that governs their say in the room – a function of both their governance tokens and their non-transferable vote record – a large position mints its own share of both, at the published rate, but it can never take the record another member minted. There is no council to authorise it and no discount to argue about: the payout is computed from the contract's own state at the moment of the call.

That does not make Caper better at running a payroll, which is the thing Beefy demonstrably does well and in public. It makes the two answer different halves of the same question. Beefy's design asks how a DAO with no seigniorage sustainably pays its people; Caper's asks what a member can do about it when they conclude the answer is wrong.

References

• Beefy DAO, beefydao.eth Snapshot space – 130 proposals, 11,067 followers, quorum 1, delegation-aware BIFI strategy across five sources (read via the Snapshot GraphQL hub, 6 August 2026).
• Beefy DAO, BIP:101 Contributor Funding H2 2026 – $145,500 per month, departmental breakdown, and the quarterly-to-six-month rationale.
• Beefy DAO, BIP:102 Staworth Renewal H2 2026 – $10,000 + 20% VAT per month, delivery report, and the offsetting reduction in BIP:101.
• Beefy DAO, BIP:99 Fair Value Buybacks – the 21 April 2026 trigger and the Treasury Council's fair-value definition.
• Beefy docs, Governance, Treasury and Contributor Compensation – the legislature/executive split, the 4-of-7 Treasury Council, and the stablecoin-payment preference.
• Beefy docs, $BIFI Token, Fee Batch and Incentive Programmes – the 80,000 fixed supply, the fee split, and the anti-capture case for the BIFI Pool and Vault.
• BIFI token contract 0xB1F1…b1f1 on Ethereum – totalSupply() returns 80,000 exactly, verified 6 August 2026.
• Beefy, beefyfinance/beefy-contracts and beefy-v2 – both live and unarchived, last pushed 18 August 2026 and 2 September 2026 respectively (GitHub REST pushed_at, read 3 September 2026).