In Bitcoin Core cli, how can I list *all* transactions of an address?

[NotATether]

Not just the ones that the Bitcoin Core client made. listtransactions won't work if I've just imported a few addresses and did a rescan, because no transactions have been made with the wallet and it returns an empty list. gettransaction works if txindex option is set, but I need to get the transaction IDs first, ideally only with Core. So how can I get a list of all txids for a wallet or address inside a wallet?

[1715446615]

1715446615

[1715446615]

1715446615

[1715446615]

1715446615

[1715446615]

1715446615

[RickDeckard]

Have you tried using listunspent instead of listtransacttions? The code would be something like this:

Code:

bitcoin-cli listunspent 1 9999999 '["add1", "add2", ...]'

According to ChainQuery[1] that command will give you a list of all unspent transaction outputs for the addresses that you want. The result will be a list that will include the transaction ID (txid) for each UTXO. I've set the minconf and maxconf to their default values, but you are free to play around with those numbers.
[1]https://www.chainquery.com/bitcoin-cli/listunspent

[nc50lc]

So how can I get a list of all txids for a wallet or address inside a wallet?

For imported address within your wallet., you can use listreceivedbyaddress but with the address arg to filter it.
Otherwise it'll list the whole wallet's receiving addresses' TXID list. (excluding change for HD wallet)

Example command:

Code:

bitcoin-cli listreceivedbyaddress 0 false true "address"

(works with imported addresses via importaddress)

[NotATether]

Thanks guys, but I just realized that listtransactions can take a parameter argument: "include_watchonly" that toggles the display of transactions from imported addresses. Not sure why this is defaulting to false as it would be really useful behavior to have on. But anyway, the listreceivedbyaddress RPC also works as well.

[nc50lc]

-snip- Not sure why this is defaulting to false as it would be really useful behavior to have on. But anyway, the listreceivedbyaddress RPC also works as well.

You must be using a legacy wallet (non-descriptor).
The wallet where you execute the command should have the "disable_private_keys" argument set to "true" when it's created.
In the GUI, the check box with the same name "Disabled Private Keys" should be ticked.

In Descriptor wallets, it's not possible to import plain address descriptors to a non-watching-only wallet so this wouldn't have happened.

[NotATether]

-snip- Not sure why this is defaulting to false as it would be really useful behavior to have on. But anyway, the listreceivedbyaddress RPC also works as well.

You must be using a legacy wallet (non-descriptor).
The wallet where you execute the command should have the "disable_private_keys" argument set to "true" when it's created.
In the GUI, the check box with the same name "Disabled Private Keys" should be ticked.

In Descriptor wallets, it's not possible to import plain address descriptors to a non-watching-only wallet so this wouldn't have happened.

Yes, I explicitly created a legacy wallet for the purposes of testing some Python core that uses the RPC, so that I don't have to spin up a bunch of altcoin nodes as well (except for maybe DOGE, which has seemingly removed any way of selecting wallet files via createwallet and -rpcwallet).