Use Once Addresses from the Daemon

[sdp]

This feature idea is for the context of daemon mode of any Bitcoin wallet that accepts connections via RPC.  This includes the standard node that accepts connections but also Electrum does this also.

I am not sure about BitcoinD, but Electrum can give other software the capability to ask for and recognize the receipt of Bitcoin via RPC and direct calls to the command line but while waiting for a payment, a similar program will get the same new address, and the donation address that came from that wallet some time ago may also be the same.

Here I refer to "wallet daemon" as any wallet that can accept connections for wallet functionality to other software.

An external client (that is a program that is allowed to connect to it, via for example TCP,  should be able to request an new address and to simultaneously have it internally marked within the wallet daemon process in a way so that future requests for new addresses never include this address.  At the same time, requests to watch the address should be still available.

Another way of expressing this idea is that the new address would be a secret known only by the wallet daemon, and the particular client program that asked for it and whoever or whatever the client program shares it with presumably whoever is being asked to pay.

Perhaps some of you know of several wallets that already do this. I think these changes require a kind of wallet that needs to be backed up more than once, I doubt a change like this would be paletable to the developer of Electrum.  So please tell me which wallet daemon's have this feature if one exists.

sdp

[Kruw]

An external client (that is a program that is allowed to connect to it, via for example TCP,  should be able to request an new address and to simultaneously have it internally marked within the wallet daemon process in a way so that future requests for new addresses never include this address.  At the same time, requests to watch the address should be still available.

Another way of expressing this idea is that the new address would be a secret known only by the wallet daemon, and the particular client program that asked for it and whoever or whatever the client program shares it with presumably whoever is being asked to pay.

Perhaps some of you know of several wallets that already do this.

Wasabi Wallet has what you are looking for. Here is the documentation: https://docs.wasabiwallet.io/using-wasabi/RPC.html

I think these changes require a kind of wallet that needs to be backed up more than once, I doubt a change like this would be paletable to the developer of Electrum.  So please tell me which wallet daemon's have this feature if one exists.

This is a solved problem: When you use BIP39, you only need to keep a single backup of a 12 word seed in order to generate an ~infinite number of new addresses.