From 5f663e3b3d4607032f765eaabb08ff379b6010d1 Mon Sep 17 00:00:00 2001 From: Sergei Tikhomirov Date: Wed, 7 Aug 2024 15:41:41 +0200 Subject: [PATCH] clarify path to immutability Co-authored-by: fryorcraken <110212804+fryorcraken@users.noreply.github.com> --- standards/core/rln-contract.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/standards/core/rln-contract.md b/standards/core/rln-contract.md index 0c47059..6371177 100644 --- a/standards/core/rln-contract.md +++ b/standards/core/rln-contract.md @@ -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