[AIP-16] Multisig performances updates

Authors
Emiliano Bonassi (protocol multi-sig)

Summary
Updates on multisig performances. Changes:

  1. 0x6429602699fEC6D205e0b9531C7f33476BA11Fb0, exit from grace period
  2. 0x4702D39c499236A43654c54783c3f24830E247dC, to be replaced/removed
  3. 0x3CBFFF3E75881c1619eaa82DC724BDEE6fF6ED19, put in grace period
  4. 0x337F8f3316E1326B3188E534913F759460bd57CB, put in grace period

Motivation and Background
Below, last month performances (extracted 9/9/22) and proposed actions.

Everything looks great, some improvements available. Proposed changes based on current framework:

Treasury

  • 0x4702D39c499236A43654c54783c3f24830E247dC was in grace period but did not recover (still 0% signed), consider replacing
  • 0x337F8f3316E1326B3188E534913F759460bd57CB did not sign any tx this month, consider entering grace period

Protocol

  • 0x3CBFFF3E75881c1619eaa82DC724BDEE6fF6ED19, low performance (20%), consider entering grace period
  • 0x3dB7FCD09cF12df1b8978ddf66F8bbF9f039eDd8, did not sign any tx this month, consider entering grace period
  • 0x2BE293361aEA6136a42036Ef68FF248fC379b4f8, low performance (20%) and was in grace period, consider replacing
  • 0x6429602699fEC6D205e0b9531C7f33476BA11Fb0, performed exceptionally (100%) and was in grace period, consider no more in grace period

Said that, my considerations, in the protocol msig, I would not replace 0x2BE293361aEA6136a42036Ef68FF248fC379b4f8 and would not put in grace period 0x3dB7FCD09cF12df1b8978ddf66F8bbF9f039eDd8.

That’s because the objective of the framework is to incentivise overall participation and those wallets performed very well in the treasury msig. So I would propose too to refine the framework considering aggregated performances across all msigs.

— RAW DATA —

Treasury

total txs: 4
signer                                      %   
0x2BE293361aEA6136a42036Ef68FF248fC379b4f8 100.0
0x3dB7FCD09cF12df1b8978ddf66F8bbF9f039eDd8 100.0
0xB65c1Ab1bF106F86a363dC10230a4AF11cCD063E 100.0
0xC02ad7b9a9121fc849196E844DC869D2250DF3A6  50.0
0x4Ab5E3F0b2d1604dD2002CfEcA6163802D74c6Cb  50.0
0x4702D39c499236A43654c54783c3f24830E247dC   0.0
0x337F8f3316E1326B3188E534913F759460bd57CB   0.0

-- Signers Time To Confirm (p=0.95) --
signer
0x3dB7FCD09cF12df1b8978ddf66F8bbF9f039eDd8   0 days 00:00:00
0x4Ab5E3F0b2d1604dD2002CfEcA6163802D74c6Cb   0 days 17:00:40
0xC02ad7b9a9121fc849196E844DC869D2250DF3A6   1 days 01:08:19
0x2BE293361aEA6136a42036Ef68FF248fC379b4f8   1 days 04:02:26
0xB65c1Ab1bF106F86a363dC10230a4AF11cCD063E   1 days 04:59:21

Protocol

total txs: 5
signer                                      %   
0x30019eB135532bDdF2Da17659101cc000C73c8e4 100.0
0x6429602699fEC6D205e0b9531C7f33476BA11Fb0 100.0
0x512fce9B07Ce64590849115EE6B32fd40eC0f5F3  60.0
0xF01Cc7154e255D20489E091a5aEA10Bc136696a8  60.0
0x2BE293361aEA6136a42036Ef68FF248fC379b4f8  20.0
0x3CBFFF3E75881c1619eaa82DC724BDEE6fF6ED19  20.0
0x3dB7FCD09cF12df1b8978ddf66F8bbF9f039eDd8   0.0

-- Signers Time To Confirm (p=0.95) --
signer
0x30019eB135532bDdF2Da17659101cc000C73c8e4   0 days 00:00:00
0x2BE293361aEA6136a42036Ef68FF248fC379b4f8   0 days 00:16:19
0x82621E3a9584013B166f6939677Df67793530C7B   0 days 00:17:47
0x3CBFFF3E75881c1619eaa82DC724BDEE6fF6ED19   0 days 00:18:32
0x512fce9B07Ce64590849115EE6B32fd40eC0f5F3   0 days 00:41:20
0xF01Cc7154e255D20489E091a5aEA10Bc136696a8   0 days 01:00:21
0x6429602699fEC6D205e0b9531C7f33476BA11Fb0   0 days 04:33:48

Voting

For:

  1. 0x6429602699fEC6D205e0b9531C7f33476BA11Fb0, exit from grace period (protocol)
  2. 0x4702D39c499236A43654c54783c3f24830E247dC, to be removed and replaced with @Alunara wallet 0x71df067D1d2dF5291278b7C660Fd37d9b6272b4C (treasury)
  3. 0x3CBFFF3E75881c1619eaa82DC724BDEE6fF6ED19, put in grace period (protocol - 4 weeks)
  4. 0x337F8f3316E1326B3188E534913F759460bd57CB, put in grace period (treasury - 4 weeks)
  5. update framework considering wallet aggregated performances across multisigs

Against: No action

Looking forward for your feedback!

5 Likes

Hey, awesome detailed work. There have been no comments for about 8 days now which I think means that a lot of people are not really tracking the implications of this. Have you had any direct feedback?

1 Like

Thanks Trantor for the follow-up. Partially, I am going to bring the discussion back to the signers. Will revert here then.

1 Like

all looks good to me. in support

2 Likes

Great work, brother, I’m in full support.

1 Like

Looks like a good and fair approach, I’m in full support of this! :muscle:

1 Like

Hi, looks perfect I am in full support.

1 Like

Hello, this looks awesome, thank you for this!

1 Like

I’ve been asked to replace one of the signer on the treasury multisig, and would love to do so!

My experience with Gnosis and multisigs in general are primarily with Llama Airforce, where I am one of the signers for both the operational and treasury multisigs. In addition to that, we are also working together with Redacted Cartel’s Pirex which also involves an operational multisig. Before all that, I’ve also submitted a few Alchemix treasury proposals and of course am involved with Curve + Convex governance.

I think I’d be a good signer, as I believe I can respond in a timely manner, have the technical knowhow as a dev and DeFi native and stay neutral and objective in times of troubles. Also, I’m in it for the tech :smile:

4 Likes

Thank you @Alunara for proposing!

I’ll update the proposal on Monday, so signer can confirm their preference.

1 Like

Proposal updated adding @Alunara as new signer

Please @solarcurve @Franklin @philjfry and all the community members express your interest

@Alunara share your governance wallet address as reply to this post

Goal is to move the proposal to the final stage and put on the next voting round this Thursday (29/9/22)

Thank you all!

One minor thing I would like to discuss is that sometimes these transactions are executed so fast that some members of certain time zones may not even have the chance to sign. I would hate to see someone booted just because the rest of the team was on top of their game for routine transactions. I also worry that this sort of strict performance metric stuff might encourage people to sign before verifying the transaction fully, since some transactions literally get fully signed in a matter of minutes. I’m curious if anyone has any thoughts on this topic

Thank you for handling all this @emilianobonassi

looks all g to me

can also vouch for Alunara to join the treasury siggy

My multisig wallet address is: 0x71df067D1d2dF5291278b7C660Fd37d9b6272b4C

1 Like

Thank you @Alunara

Updated the proposal with the address, @Trantor gtg for next steps

1 Like

@mikeb I share the same feedback, thanks for reporting.

I did not find an improvement yet. We could add an artificial minimum time and reduce the scoring if signed transaction is not correct and might be repeated. We could also add explicit rotation and extend the review period from 1 month to 2 or 3.

Let’s continue the brainstorming on a separate thread, in the forum or on telegram. Feel free to open a new topic and link it here.

Snapshot is live.

https://vote.aura.finance/#/proposal/0x0bcc3d56cde6ee4c3ac673540a540146143bb7830500037b717d7899fe17b628

1 Like

Snapshot passed! Thank you all.

Moving to the enact phase. Treasury msig tx should be prepared for the following:

  1. 0x4702D39c499236A43654c54783c3f24830E247dC, to be removed and replaced with @Alunara wallet 0x71df067D1d2dF5291278b7C660Fd37d9b6272b4C (treasury)

cc @Trantor @Franklin

1 Like

Congratulations, brother!

2 Likes