The Beanstalk DAO is responsible for the formation of two independent, symbiotic organizations with distinct mandates: Beanstalk Farms and Bean Sprout (a Beanstalk accelerator program).
Beanstalk Farms is a decentralized development organization of core contributors working on Beanstalk, operating across the stack on technical and non-technical problems.
Neither Beanstalk Farms nor Beanstalk have a treasury. Beanstalk Farms has historically been funded by the Beanstalk DAO. Beanstalk Farms proposes budget BIPs that mint Beans to cover operating expenses and compensate contributors. Budget funds are custodied by the Beanstalk Farms Multisig (BFM). Larger payments in non-Bean assets like audits have historically been paid for via Fundraiser.
Past BIPs that funded Beanstalk Farms:
BIP-8: Beanstalk Q1 2022 Budget (included Beanstalk Farms and Bean Sprout)
Monthly reports on how Beanstalk Farms is spending its budget can be found here.
The Beanstalk Farms Committee (BFC) is the group of Beanstalk Farms contributors that has discretion over the Beanstalk Farms budget, including contributor compensation. The BFC hires at and dismisses contributors from Beanstalk Farms.
Beanstalk Farms Committee Proposals, or BFCPs, are proposals related to personnel on the BFC. The Beanstalk DAO governs the BFC. The Beanstalk DAO adds contributors to the BFC via BFCP-As, removes contributors from the BFC via BFCP-Bs, and renews the terms of existing BFC members via BFCP-Cs.
Any Stalkholder with 0.1% of the Stalk supply can propose a BFCP-A or BFCP-B. There is no maximum number of BFC members, which facilitates permissionlessness.
See #bfcp for more info on each BFCP proposal type. BFCPs are proposed on the Beanstalk Farms Snapshot page. Stalkholders can vote on BFCPs on the Beanstalk UI Governance page. Past BFCPs can be read here.
Beanstalk Farms Budget Proposals, or BFBPs, are proposals related to the use of the Beanstalk Farms budget. Only BFC members can propose and vote on BFBPs.
The BFC hires contributors via BFBP-As, dismisses contributors via BFBP-Bs, and otherwise uses the Beanstalk Farms budget via BFBP-Cs.
See #bfbp for more info on each BFBP proposal type. BFBPs are proposed on the Beanstalk Farms Budget Snapshot page, which is where BFC members vote. Past BFBPs can be read here.
Beanstalk Farms budget funds are custodied by the Beanstalk Farms Multisig, or BFM. The BFM is deployed using Safe. Its m-of-n configuration is currently 4-of-7 on Arbitrum. This means any use of the budget funds must be approved by at least 4 of the 7 signers.
Beanstalk Farms Multisig Safe address: 0xd39A31e5f23D90371D61A976cACb728842e04ca9
The current BFM signers are as follows, in no particular order:
Michael Montoya
Brean
guy
sweetredbeans
mod323
aloceros
Cujo
The following Farmers serve as backup signers for the BFM, in no particular order:
pizzaman1337
CanadianBennett
MrMochi
Rotating BFM signers requires a BOP (or BIP) unless a signer voluntarily leaves the BFM or for rotating in a backup signer.
Address |
---|
The Beanstalk Farms Committee, or BFC, is the group of Beanstalk Farms contributors that has discretion over the Beanstalk Farms budget, including contributor compensation. The BFC hires contributors at and dismisses contributors from Beanstalk Farms. Read more here.
The current BFC members are as follows, in no particular order:
BFC member | End of term | Latest BFCP |
---|---|---|
Adding members to the BFC requires a BFCP-A and removing BFC members requires a BFCP-B. You can read more about BFCPs here.
The following addresses do not custody any funds and are not signers on any multisig—they are simply used by BFC members to propose and vote on BFBPs on the Beanstalk Farms Budget Snapshot page.
Address |
---|
sweetredbeans
December 2024
guy
December 2024
Rex
May 2025