rooch icon indicating copy to clipboard operation
rooch copied to clipboard
verified publisher icon rooch-network

[Framework] Upgrade policies of Rooch framework

Open pause125 opened this issue 2 years ago • 1 comments

Discuss the upgrade policies of Rooch framework. Some related discussion before: #146 and #83 .

Two basic policies: compatible, immutable.

The discussion is mainly about compatibility upgrading policy as we will definitely upgrade the framework.

There are two way to manage the upgrading process:

  1. Multi-signature.
  2. A two-phase upgrade policy coupled with the DAO system like Starcoin does.

Option 1 adopts a multi-signature approach, allowing for an upgrade once N-of-M signatures agree. It is convenient, flexible, and enables rapid iteration. Option 2 allows for the involvement of a larger ecosystem of users, including end-users. But the upgrading process may be lengthy involving proposal, public disclosure, voting, and other lengthy processes.

pause125 avatar Aug 25 '23 14:08 pause125

We can support on-chain Multi-signature for option 1

jolestar avatar Sep 01 '23 00:09 jolestar

We support UpgradeCap and also support Bitcoin native multisign accounts. The application can customise the upgrade policies based on UpgradeCap.

jolestar avatar Sep 09 '24 03:09 jolestar