You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable developers to build application where the users pays for their own credentials.
In this flow, the user pays for their own membership directly with the contract.
In terms of credentials management:
import and export to encrypted JSON keyfile
Credentials to be generated either with or without seed depending on the context..
E.g. Seeded with Wallet signature to help with recovery.
Finally, in terms of messages sending: ensuring that a user cannot shoot themselves in teh foot by sending too many messages. Likely to happen at a general SDK layer rather than protocol layer.
Justification
This is the simplest and most censorship-resistant usage of RLN where a user interacts directly with the smart contract to start sending messages.
Notes
More advanced credentials management to be handled with RLN Credentials Security and Multiple Devices
Milestone: https://github.com/waku-org/pm/milestone/6
Summary
Ref: (A) #102
Enable developers to build application where the users pays for their own credentials.
In this flow, the user pays for their own membership directly with the contract.
In terms of credentials management:
Credentials to be generated either with or without seed depending on the context..
E.g. Seeded with Wallet signature to help with recovery.
Finally, in terms of messages sending: ensuring that a user cannot shoot themselves in teh foot by sending too many messages. Likely to happen at a general SDK layer rather than protocol layer.
Justification
This is the simplest and most censorship-resistant usage of RLN where a user interacts directly with the smart contract to start sending messages.
Notes
Epics
The text was updated successfully, but these errors were encountered: