Marininha on Nostr: Nobody asked for my opinion and maybe some people will have better ideas to add up, ...

Nobody asked for my opinion and maybe some people will have better ideas to add up, but as a PO for a Nostr client, I wouldn’ see much value in on-chain zaps.

But f they’d need to exist for a reason as “we’d like to be able to send higher amounts of sats per transaction”, my requirements would be to:

- check feasibility of creating a built-in online wallet that is decoupled from npub/nostr nsec. It shouldn’t be mandatory for all users using the client, but rather an optional feature, with the Lightning wallet (native or connected via NWC) being the standard. Its acceptance can be requested at the setup of the client, but it should als be available in the settings for users who decide to adhere later;
- ideally, users could be able to connect their existing on-chain wallets of choice to the client as an option;
- enable silent/ anonymous payments or ideally enabling the possibility of generating single-use addresses, decoupling transactions from Nostr npub;
- The user should receive an alert about the fees involved before confirming/signing the transaction;
- The transaction would only be feasible to another on-chain wallet (but I understand this is already the case).
- of course in a decentralised system there will be no terms of service or liability, but there could be some kind of tooltip or FAQ explaining to non-tech-savy users what is the difference between on-chain and Lightning to enable informed decisions.

What would you suggest?