Skip to content

nledo/multisig-ops

 
 

Repository files navigation

Welcome to the Balancer Multisig Operations Repo

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

The Multisigs

Information about all of the Multisigs that the Maxis may load transactions into are in multisigs.md

Uploading transaction JSONs as part of Balancer Governance

Balancer Governance requires that a link to a PR request in this repo with a gnosis-safe transaction builder JSON is included.

PR's should be to include a single file named BIP-XXX.json in the BIPs directory where XXX is the number of the BIP.
Payloads are batched per week so the payload should be put into the BIPs/YYYY-W## to specify which week number/year it should run on.
Your file may be moved into a scheduled directory if it is not already in one.

The PR should include the BIP title as it's commit/pr text.

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 multisig
  • chainId: Must be the numeric chain ID of the chain to run on
  • bipNumber: The BIP number of the governance that authorizes this change

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.

Examples

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

Chain Link Upkeeps

The Maxi's have started using Chain Link 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.

Governance Process

Verbose and up-to-date docs about the balancer governance process can be found on docs.balancer.fi

Fees and Bribs

  • Check out the Bribs for artifacts from our Core Pools Fee redirection processes (BIP-19)
  • Check out FeeSweep for artifacts and info about our protocol fee processing activities

Assorted tooling

  • tools is a somewhat messy directory with a bunch of reports/automations and scripts we use to deal with the various workloads.
  • action-scripts is where we build more final code and integrate more hashed out automations into github actions.

Need Help

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.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 66.3%
  • Solidity 33.3%
  • Shell 0.4%