logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-05 23:53:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update rln-contract.md

Browse Source
This commit is contained in:
Jimmy Debe 2025-05-21 08:18:55 -04:00 committed by GitHub
parent b29961df5c
commit 8056725a96
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
standards/core/rln-contract.md
View File

@ -52,7 +52,7 @@ see [32/RLN-V1](https://github.com/vacp2p/rfc-index/blob/main/vac/32/rln-v1.md).
Membership registration MAY be initiated by a different entity from the one that controls the RLN `identity_secret`, Membership registration MAY be initiated by a different entity from the one that controls the RLN `identity_secret`,
which is associated with the respective RLN `identity_commitment`. which is associated with the respective RLN `identity_commitment`.
Therefore, the holder role MAY be assigned to a blockchain address that does not control the `identity_secret`. Therefore, the holder role MAY be assigned to a blockchain address that is not derived from the `identity_secret`.
The contract SHOULD verify that the `identity_commitment` is valid. The contract SHOULD verify that the `identity_commitment` is valid.
When authorizing membership-related requests, When authorizing membership-related requests,
the contract MUST distinguish between the holder and non-holders, the contract MUST distinguish between the holder and non-holders,
@ -119,7 +119,7 @@ Different line types denote the types of state transitions:
| Thin (`--`) | Transaction | MAY be initiable by any user. | | Thin (`--`) | Transaction | MAY be initiable by any user. |
| Dotted (`-.-`) | Time progression | MAY be applied lazily. | | Dotted (`-.-`) | Time progression | MAY be applied lazily. |
Transaction-triggered state transitions MUST be applied immediately based on the blockchain transaction time. Transaction-triggered state transitions MUST be applied immediately.
When handling a membership-specific transaction, the contract MUST: When handling a membership-specific transaction, the contract MUST:
- check whether the state of the involved membership is up-to-date; - check whether the state of the involved membership is up-to-date;