The Beanstalk Community Multisig (BCM) custodies ownership of the Beanstalk contract. The BCM has the exclusive ability upgrade Beanstalk. In the future, it is expected that BIPs will reimplement permissionless governance and revoke these abilities from the BCM.
Per the Verifying and Signing Transactions section of the BCM Process, all BCM Signers are expected to know how to verify diamondCut data and confirm they have verified transactions by uploading signed messages to Arweave.
See BCM Process and BCM Dashboard for more information.
If you aren’t familiar with EIP-2535 Diamonds and the corresponding data structures for the inputs to a diamondCut call (facet cuts, the init address, etc.) that upgrades an Ethereum Diamond, check out these resources before continuing:
In order to set your environment up in preparation for following the Runbook to test a BIP, follow this guide: