Links

diamondCut JSON:

Overview

Init Contract

InitBipSeedGauge: 0x6eF9cC52Eb37e0dE9592960c0c894a1000ac7dDf

Facets Being Added

Facets Being Deprecated

Verifying the Transaction

Setup

1. Follow 🏗️How to Setup Environment, pulling and compiling the latest changes on the bip39-seedGauge branch.

The Diamond Cut Transaction

Add the following bip45enc task to hardhat.config.js per ⛳How to Verify Facet Changes.

You can verify that the following data value in the final line of code is the one that corresponds to the BIP transaction by comparing it with the Raw data field on the Safe multisig transaction.

Verifying the Diamond Cut

1. Follow ⛳How to Verify Facet Changes.
2. Verify there are no remaining function selectors from the Facets Being Deprecated section above.
3. Verify that all function selectors from the Facets Being Added section above are present.

Verifying the Deployed Code

1. Follow 🧑‍💻[Seed Gauge] How to Verify Deployed Code.
2. Verify that each facet has verified code on Etherscan.

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-45 with BCM transaction nonce 69, Safe transaction hash 0x77ca4fcf8c8e7a1876025f236eaacc429342e83a55854e98d8164a5f90e52975, commit hash ac8e681c7daa7cb046c1e405b27e50e7e44c0504 and Snapshot proposal https://snapshot.org/#/beanstalkdao.eth/proposal/0xec4d347918be45d2ec92de0c87a8802ab8e2017d17b5e5809c91a02ea6b9ae66.