New answers tagged

0

I know this is an old question, but for anyone reading currently: api.fullstack.cash offers an endpoint for this, but this is mainly a paid API service, and isn't always free. https://api.fullstack.cash/docs/#api-ElectrumX_/_Fulcrum-Transactions_for_an_array_of_addresses


0

I've had the same issue after restoring from wallet.dat. It's probably a bug described in https://github.com/bitcoin/bitcoin/issues/20293. Possible way to fix it is by setting an empty label to the address that became change: bitcoin-cli setlabel "{address}" ""


1

The GUI's debug console operates similarly to a shell. It needs quotes around the entire JSON string so that it is first interpreted as a string before the JSON is parsed. Then, if you used double quotes, you need to escape the quotes that are part of the JSON so that they aren't misinterpreted. A valid way of writing this command is getblocktemplate "{\...


1

bitcoind internally treats all amounts as an integer and only displays the value as a decimal for the RPC. Formatting for display does not introduce any floating point precision issues as it still just does integer conversion with some string formatting to make it look like a decimal. So it is perfectly safe to multiply by 100000000 to get an integer amount ...


Top 50 recent answers are included