logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-02 14:13:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

clarify definition of tx sender as membership keeper

Browse Source
This commit is contained in:
Sergei Tikhomirov 2024-08-30 11:11:56 +02:00
parent 586d70bfba
commit 818ce98476
No known key found for this signature in database
GPG Key ID: 6A1F8ED9D6538027
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -45,7 +45,12 @@ The contract MUST provide the following functionalities:
- withdraw a deposit.
A membership _holder_ is the entity that controls the secret associated with the respective RLN commitment.
A membership _keeper_ is the entity that controls the Ethereum address used to register that membership.
A membership _keeper_ is the sender of the transaction that registered that membership.
Transaction sender in this context is defined as `msg.sender` in Solidity semantics.
The contract MUST support transactions sent from externally-owned accounts (EOA).
The contract MAY also support meta-transactions sent via paymasters or relayers,
which MAY require additional authentication-related logic.
The holder and the keeper MAY be different entities for the same membership.
When authorizing membership-related requests,
the contract SHOULD distinguish between the keeper and non-keepers,