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.

BCM Dashboard

docs.bean.money

Table of Contents

• Table of Contents
• Docs
• Getting Started
• How To Verify a BIP

Docs

📜

Verification Guides

🏗️

How to Setup Environment

🔍

How to Interpret Diamond Cut Data

How to Submit Safe Txns

💵

How to Verify Mint Txns

🧑‍💻

[OLD] How to Verify Deployed Code

🧑‍💻

[Seed Gauge] How to Verify Deployed Code

⛳

How to Verify Facet Changes

Getting Started

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:

• EIP-2535
• 🌱 Beanstalk 🤝 EIP-2535 💎
• 🔍How to Interpret Diamond Cut Data

In order to set your environment up in preparation for following the Runbook to test a BIP, follow this guide:

• 🏗️How to Setup Environment

Docs:

• 📜Verification Guides: How To Guides
• 📖BIP Runbooks: Procedures to follow to verify a BIP, along with verified message signatures from BCM Signers for that BIP.

How To Verify a BIP

Using the information in the 📖BIP Runbooks, verifying a BIP transaction should involve at least steps 1-7:

1. Execute the diamondCut and verify that the correct facets and selectors have been added, changed or removed.
• ⛳How to Verify Facet Changes
2. Verify that each facet that is added/changed has the same source code as the pull request.
• 🧑‍💻[OLD] How to Verify Deployed Code
3. Verify that each facet that is added/changed has verified code on Etherscan.

4. Confirm that the facet addresses in the diamondCut match the addresses listed in the Contract Changes section of the written Snapshot proposal.
5. Verify that the _init address has verified code on Etherscan.
6. If the _init address is the InitMint address, verify that the correct number of Beans are minted to the correct address based on the Beans Minted section of the written Snapshot proposal.
• 💵How to Verify Mint Txns
7. If the _init address is neither the InitMint address nor the null address, verify that the contract has the same source code as the pull request.
• 🧑‍💻[OLD] How to Verify Deployed Code
8. Review the pull request code changes.
9. Review any audit reports.