Roland

Example response: ``` {"result":{"balance":2575000,"max_amount":0,"budget_renewal":""},"result_type":"get_balance"} ``` This gives an error with rust-nostr: ``` Err(JSON(Error("Json: unknown variant ``, expected one of `daily`, `weekly`, `monthly`, `yearly`", line: 0, column: 0))) ``` If not...

For redundancy, you should be able to connect to multiple relays. Requests should be debounced on the NWC side and all relays should be replied to no matter which relay...

apps are currently indexed by pubkey (e.g. https://nwc.getalby.com/apps/21bc9ba96fa06d8cedeca7bb2ca601c514543539c15fc2bf79df4331ea49a995) which is a problem if there are two apps for the same user that share the same pubkey. A workaround is in...

e.g. PAYMENT_FAILED is not used yet.

The Alby LNClient does not support millisat payments, but how can we ensure developers make sure that payments of only whole amounts in sats are sent? A nice error message...

Apps with no permissions should not be able to do anything

2

Now we have multiple conditionals to treat legacy NWC connection strings differently. It would be nice to remove these to simplify the code. See https://github.com/getAlby/nostr-wallet-connect/pull/172 This will break existing connection...

In https://github.com/getAlby/nostr-wallet-connect/pull/178 when introducing pay_keysend we changed from `1 permission -> 1 method` to `1 permission -> multiple methods` for payments. So it no longer really makes sense to tie...

The NWC app only connects to one LNClient so it doesn't really make sense for all the LNClient options to be packaged together. A core go package could handle all...

Consider it always ok to read node info. That is how WebLN currently works, if we are ok with that in WebLN. Maybe later we can introduce a `GetMethods` function...

Needs review before implementing. See https://github.com/getAlby/nostr-wallet-connect/pull/172