search

onflow / hybrid-custody-account

Coordinating repository for HybridCustody contract account signers
0 stars 1 forks source link

Update transaction info for upcoming key rotation process #4

Closed sisyphusSmiling closed 11 months ago

sisyphusSmiling commented 11 months ago

Closes: #1

This PR adds guidance and relevant config, transactions, and arguments for key rotation of the HybridCustody contract account into multisig management.

Communications to arrange a date & time for transaction signing is in progress, but the hope is to complete the process by the end of this week.

Note: We don't yet have a key from Niftory as their custodian is OOO, but the plan is to add them once we secure their key information. This means the account will be managed by 4/7 multisig until their key is added as the 8th.

Tagging key holders here for visibility: @austinkline @lmcmz @rrrkren @bjartek @bluesign @jacob-tucker

bluesign commented 11 months ago

Should we maybe make it 5/n ( as it will be majority when 8 signers )

sisyphusSmiling commented 11 months ago

I see what you're saying @bluesign, 5/8 would be majority. Looking to service account, it currently utilizes 4/10 authorization. I'm open to 5/8, my only concern here is that coordinating a signing party could be more difficult with a larger number of signers considering our time zone distribution.

bluesign commented 11 months ago

Not that important tbh, but to make things proper only. Service account 4/10 is another story :)

We can always start with 4/n ofc