clarify path to immutability

Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com>
This commit is contained in:
Sergei Tikhomirov 2024-08-07 15:41:41 +02:00 committed by GitHub
parent d84ac43182
commit 5f663e3b3d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -89,8 +89,8 @@ There is no limitation on the number of membership per user (apart from the glob
The contract governance is as follows:
1. the first deployment of the contract allows the `Owner` to modify certain parameters (TBD) under certain constraints (TBD);
2. at some point, the `Onwer` would renounce their privileges, and the contract will become immutable;
1. the first deployment of the contract allows the _Owner_ to modify certain parameters (TBD) under certain constraints (TBD);
2. at some point, the _Owner_ SHOULD renounce their privileges, and the contract MUST become immutable;
3. further upgrades, if necessary, can be done by deploying a new contract and migrating the membership set.
## Parameters