This repo is used to store payloads uploaded to the multisig, as well as any tooling used to generate such payloads.
You can find a FAQ about snapshot handling here: FAQ
Information about all of the Multisigs that the Maxis may load transactions into are in multisigs.md
Balancer Governance requires that a link to a PR request in this repo with a gnosis-safe transaction builder JSON is included.
bip-xxx-some_title
BIP-XXX-some_title.json
in BIPS/00proposed/
A post can now be created on the forum with the title "BIP-XXX: Some Title" linking to this PR.
Here is the minimal viable framework for a Balancer Governance acceptable payload
{
"version": "1.0",
"chainId": "1",
"createdAt": 1685637015445,
"meta": {
"name": "Transactions Batch",
"description": "",
"txBuilderVersion": "1.14.1",
"createdFromSafeAddress": "0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f",
"bipNumber": 42069
},
"transactions": []
}
All payloads MUST include the following in the global section:
createdFromSafeAddress
: That matches a known balancer multisigchainId
: Must be the numeric chain ID of the chain to run onNote that the bipNumber
will be added later, once the forum proposal has been assigned a number.
You can provide more details in name and description if you want.
The transaction list takes the format of a standard gnosis tx builder list.
We are slowly developing a library of detailed examples for how to build BIP payloads based on common actions. These examples can be found HERE
The Maxi's have started using Chainlink automation to automate some regular processes that don't need deep review.
Documentation of our various running keepers can be found in chainlink_keepers Chainlinks documation around this automation setup can be found here.
Verbose and up-to-date docs about the balancer governance process can be found on docs.balancer.fi
You can contact Tritium, Solarcurve or any of the BAL Maxis on the Balancer Discord for help getting your JSON PR submitted. We can also just do it for you if that's what you'd prefer.