Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add dao multisig on fantom #221

Merged
merged 6 commits into from
May 21, 2024
Merged

chore: add dao multisig on fantom #221

merged 6 commits into from
May 21, 2024

Conversation

Tritium-VLK
Copy link
Member

@Tritium-VLK Tritium-VLK commented Mar 4, 2024

Solves #216

@Tritium-VLK Tritium-VLK requested a review from Xeonus March 4, 2024 19:31
@Tritium-VLK
Copy link
Member Author

@Xeonus we should verify the signers on this multisig before merging this PR/make sure we have that under control. I'll take a look at it in a few days. I don't see the normal gnosis safe interface here, any chance you know how to easily see this msig in the UI?

@gosuto-inzasheru
Copy link
Member

@Tritium-VLK
Copy link
Member Author

image

Need to find more signers, right now this is a 6/11 msig with only 4 known signers. Don't think we should add this to bal_addresses until we have control of it,.

@Tritium-VLK
Copy link
Member Author

Tritium-VLK commented Mar 13, 2024

Ok so we need more of a plan here. This is what I suggest.

1: Launch a new safe on fantom with maxi signers.
2: Load up 1 tx to claim and send the beets to the safe created in 1 (@solarcurvey can load it)
3: Search the earth for enough signers to make it so and exec when we get there.
4: Bridge to the LM multisig fromt he maxi safe
5: Send to DAO multisig on Op(if there is one or leave in maxi safe if not)

I don't think the beets is that much value/is ok in a safe with Maxi signers. @Xeonus @mikebmikeb @0xDanko sound good?

@0xDanko
Copy link

0xDanko commented Mar 13, 2024

What happened to bridging it to Optimism, there's no bridge? I don't mind if you guys want to have this sitting idle or do something with it, as long as it has a gov vote to support. But honestly, it kinda strays away from Maxis scope of work moving forward if you're not doing anything with it. Plus, this could sit anywhere else that is not under management of US-persons for no reason. Even giving it to Karpatkey seems like a better idea IMO.

@Tritium-VLK
Copy link
Member Author

Tritium-VLK commented Mar 13, 2024

@0xDanko updated the bip to get it to OP. Karpatkey only operates on mainnet right now, so that's not really an option at the moment, but I agree. If the tokens end up being worth considerable value (more than a few hundred k) we should move them to a DAO signer managed safe.

@0xDanko
Copy link

0xDanko commented Mar 13, 2024

@Tritium-VLK
Copy link
Member Author

Note that I asked Fernando to try to get in contact with 2-3 of the unknown signers on the safe so we can take control and recover the beets.

@gosuto-inzasheru
Copy link
Member

ah i never saw this pr

i think it can be closed, these changes are already included in #264 and #267

also needed some adjustments in the multisig ops repo to get sims going (https://github.com/BalancerMaxis/multisig-ops/pull/916/files):

Screenshot 2024-04-25 at 15 17 12

@gosuto-inzasheru gosuto-inzasheru changed the title chore: Add beets vestor and dao multisig on fantom. chore: add dao multisig on fantom May 20, 2024
@gosuto-inzasheru
Copy link
Member

only diff now is the dao msig on fantom, which is good to have on file of course

@Tritium-VLK Tritium-VLK merged commit 9c0f04e into main May 21, 2024
3 checks passed
@Tritium-VLK Tritium-VLK deleted the beets_vestooor branch May 21, 2024 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants