feat: Allow to configure RLN via the REST API

[alrevuelta]

Allow to configure RLN via the REST API, by loading a keystore + password.

• Allow RLN keystore to be loaded from REST API.
• Modify API and spec if needed.

To be defined:

• Does the rest api override the configured keystore from cli?
• Is it persisted after restart?
• Security implications? Passing keystore + password?

Unsure if we should develop this feature, but creating a tracker for discussion.

[alrevuelta]

geth for example has a command to import keys, but seems they don't have an rpc endpoin to do so, unsure if the reason is security.
geth account import

in case it can serve for inspiration on wether to pursue this feature or not + alternatives.

https://geth.ethereum.org/docs/fundamentals/account-management#creating-accounts
https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-personal
https://geth.ethereum.org/docs/tools/clef/introduction

[Ivansete-status]

Hi @alrevuelta , is this still relevant considering the upcoming Deliverable RLNv2 Web management interface where we want to manage the RLN membership from the browser?

( @fryorcraken correct me if I'm suggesting something weird .)

[alrevuelta]

Hi @alrevuelta , is this still relevant considering the upcoming Deliverable RLNv2 Web management interface where we want to manage the RLN membership from the browser?

I would say its still needed, even with that deliverable. Am i missing something?

[fryorcraken]

I would cut this scope and start simpler, by assuming that a keystore file is provided to wakunode2.
Said keystore file coming from the RLNv2 Web management interface.

Once current RLN Mainnet is delivered, specifically waku-org/pm#286, we can review how we want to handle membership acquisition in native application (e.g. Status), and whether this is something we want to do in nwaku code (not convinced).