From 586d70bfba02e72450724765b95a699a0aa9802f Mon Sep 17 00:00:00 2001 From: Sergei Tikhomirov Date: Fri, 30 Aug 2024 10:54:11 +0200 Subject: [PATCH] clarify parameter update implications for existing memberships --- standards/core/rln-contract.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/standards/core/rln-contract.md b/standards/core/rln-contract.md index 2a7b5e3..54fbb8b 100644 --- a/standards/core/rln-contract.md +++ b/standards/core/rln-contract.md @@ -170,11 +170,17 @@ Deposit withdrawal is subject to the following conditions: At initial mainnet deployment, the contract MUST have an _Owner_. The _Owner_ MUST be able to change the values of all contract parameters. +The updated parameter values MUST apply to all new memberships. +The parameters of existing memberships MUST NOT change if the _Owner_ updates global parameters. +The contract MAY restrict extensions for memberships created before the latest parameter update. + The _Owner_ MUST be able to pause any of the following contract functionalities: - register a membership; - extend a membership; - withdraw a deposit. +The + At some point, the _Owner_ SHOULD renounce their privileges, and the contract MUST become immutable. If further upgrades are necessary,