This post summarizes the current multisig used by Leagues on different chains.
- Treasury addresses
- Hypernative integration
- Multisig best practices framework post by @emilianobonassi
Recently, some updates and changes were made to the Leagues’ multisigs. This post summarizes the addresses being used.
Idle DAO’s Leagues currently manage 8 Safe multisig with different purposes, signers and thresholds for execution
- On Ethereum we have 4 addresses: 2 used by Leagues (Treasury and Development) for daily operations, 1 used to cast stkIDLE on-chain voting preferences and one for emergency pausing of the protocols.
- On Polygon we have 3 addresses: 1 used by Leagues for daily operations and 1 used to collect the fees on-chain. On Polygon zkEVM we have only 1 address again used by Leagues.
- On Optimism we have 1 address that will be used to receive and later distribute the grant funds coming from the OP foundation.
The signers of these multisigs are core contributors and, sometimes, advisors.
|Polygon zkEVM||0x13854835c508FC79C3E5C5Abf7afa54b4CcC1Fdf||TL multisig||3/5|
For a matter of completeness, we have also run a multisig performance analysis using Multisight on the Treasury League multisig on Ethereum, i.e. the most active.
Multisig performances are often measured in terms of the single signers KPIs such as:
- the number of transactions submitted, confirmed and executed over the total number of transactions
- the average confirmation time (ACT) elapsed from the transaction proposal and the effective signing by a signer
Below are the TL multisig performances in the last year (Sep 2022 to Sep 2023):