Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions FURPS/application/rln_membership_management.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@

1. RLN membership details can be exported and imported.
2. Deployment details (address, chain id) are persisted by library and in exports.
3. Create script to extend existing memberships.

## Reliability

Expand Down
1 change: 1 addition & 0 deletions draft-roadmap/integrate_rln_with_waku_api.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ See deliverables.

- U1. RLN membership details can be exported and imported.
- U2. Deployment details (address, chain id) are persisted by library and in exports.
- U3. Create script to extend existing memberships.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a FURPS can't really be "create something that implement the FURPS.

This is more of a supportability item:

CLI command to extend existing memberships.

Can we please clarify with infra how they want the command to get the wallet signature in a secure manner?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yakimant - considering previous Franck's comment, how do you envision the best way to extend the current membership in Waku's fleets ? ( feel free to make this question extensive to other Infra colleagues .)


- R1. Import and exports are interoperable across all implementations.

Expand Down