3

The simple answer is that when the parameter '%U' is missing from the 'Exec' line in a gnome/Ubuntu desktop file, the OS creates a new instance whenever the application is called (in this case by the browser on clicking a bitcoin: link on a web page). That fails when the application can only have one instance running (bitcoin-qt by itself handles the bitcoin ...


2

Not all scriptPubKeys correspond to an address. The address field is provided for those that do, and is omitted for those that don't. Your example contains a P2PK scriptPubKey which does not have a corresponding address. Some blockchain explorers may extract the pubkey from a P2PK output and compute a corresponding address, but that is not technically ...


2

Bitcoin-qt does not interact with bitcoind at all. Bitcoin-qt is a full node by itself, entirely stand-alone. There is a tool shipped with Bitcoin Core called bitcoin-cli which allows RPC commands to be issued. You can certainly interact with your Bitcoin Core node from another machine via the RPC (remote).


2

This occurs because the genesis block is a special block. It is not written to disk like all other blocks are. It cannot be undone so there is no undo data for it. getblockstats uses the undo data (essentially a compact representation of the UTXOs spent by the transactions in a block) to calculate many of the block stats, but because the genesis block does ...


1

As @Andrew Chow said: Bitcoin-qt is not just a frontend GUI or wallet handling software. It is bitcoind with a GUI. There is a WIP project for separating things and make this possible, but it's still very early and not recommended for end users. What are some common wallets that support this feature? (trusted nodes via RPC or SPV to a bitcoind full node) ...


1

listreceivedbyaddress (and the other transaction listing RPCs) list logical transactions, not physical transactions. So it really lists transaction outputs. Additionally, they share a lot of code. Because these are logical transactions, there are some things that are hidden so that the output is not confusing to the user. One of those things are change ...


1

Is your core compiled with the wallet? Because gettransaction RPC get wallet transactions, and hence need wallet capabilities. For general transactions, you should use getrawtransaction instead. I ran it here (with wallet enabled) and works just fine.


Only top voted, non community-wiki answers of a minimum length are eligible