Links

{
    "diamondCut": {
      "diamondCut": [],
      "initFacetAddress": "0x077495925c17230E5e8951443d547ECdbB4925Bb",
      "functionCall": "0x399ae72400000000000000000000000021de18b6a8f78ede6d16c50a167f6b222dc08df700000000000000000000000000000000000000000000000000000006fc23ac00"
    }
}

Verifying the Transaction

BIP-43 has 2 parts:

1. The first calls enableModule on the BCM with the Hypernative contract (0x59C78c1C2b4b03B4530d5f46F02362e4A03eFe4d) as the module parameter. You can verify this in the 1st “action”:

2. The second mints 30,000 Beans to the Beanstalk Farms Multisig. Thus, you can follow 💵How to Verify Mint Txns verify the correct number of Beans are minted.
1. Address: 0x21DE18B6A8f78eDe6D16C50A167f6B222DC08DF7
2. Number of Beans to mint: 30,000
3. You can also verify that the diamondCut does not change any facets because the facetCuts parameter is the empty array [] :

Submitting Message Signature

Once Signers have verified the transaction, they shall submit and sign a verified message on Etherscan with their BCM address (guide).

Template message: Confirming that I have reviewed BIP-43 with BCM transaction nonce 66, Safe transaction hash 0x89da5abaf87bc6551a850a9793f221fe0b96ca2d528cd60d1a670325646a04f0 and Snapshot proposal https://snapshot.org/#/beanstalkdao.eth/proposal/0x189c67625926ceec3578b5a83424d88b42bafac6e0dc5514a29ca46ecc018011.