New answers tagged json-rpc
2
What does getbalance give me?
getbalance returns the total available balance according to your configuration. If you have -spendzeroconfchange set to 1 (the default), this is your total confirmed + unconfirmed balance.
Whichever it gives me, I can then add or subtract the pending value to get the other value.
By default getbalance - getunconfirmedbalance =...
1
There are two cases here:
Block with the tx became orphaned and the transaction is still valid. In this case it is returned to the mempool. gettransaction will return unconfirmed transaction detail
Another conflicting transaction got confirmed ( having same inputs). In this case existing txid becomes invalid and it is discarded
0
It's the same wallet, data?
This depends on your configuration like -datadir. This can be specified by command line, or something like a registry key value (when you are using Microsoft Windows).
Note that recent versions of Bitcoin Core supports loading multiple wallet at same time.
TL:DR: is the RPC 8332 port active when using the GUI, Vs the Daemon?
...
1
I had named my script bitcoinrpc.py and had the import bitcoinrpc. Naturally it couldn't find the package. Renamed the script and it works.
Lesson: DO NOT have a file of the same name as the package you are trying to import.
0
Ok it turned out I was a bit confused about the way fees and change is handled here. Here are the commands that worked for me:
createrawtransaction "[]" "[{\"$UADDR\":1.2},{\"$UCHANGE\":1.8}]" 0 false "{\"$UADDR\":\"$ASSET\",\"$UCHANGE\":\"$ASSET\"}"
fundrawtransaction ...
0
Implementing a rule change that all pre-existing bitcoin nodes will not follow is equivalent to creating a new altcoin network (similar to the creation of BCH, for example).
There is no sensical way for a pre-existing bitcoin node to watch for such changes, and decide that it should follow that new (otherwise invalid) chain instead. A bitcoin node can ...
3
There is no way to explicitly know that your node is on a minority-hashrate fork because to do so would mean awareness of all the new rules that makes the majority-hashrate fork valid, and then determining that more proof-of-work is accumulated on that chain. For that to be possible, you must be running an upgraded node already.
There are a few warning ...
Top 50 recent answers are included
