Some additional guidance is in share/examples/bitcoin.conf to add to Nontenda's answer.
Let's say for instance you use addnode=184.108.40.206, addnode will connect
you to and tell you about the nodes connected to 220.127.116.11. In addition
it will tell the other nodes connected to it that you exist so they
can connect to you.
connect will not do the above when you &...
When it says, "connect" it is referring to connecting in the TCP/IP sense. The vulnerability simply required you having the ability to open a TCP/IP connection to bitcoind's RPC port, which is before any concept of authentication even comes into play.
It isn't that it was possible to send JSON-RPC commands to bitcoind without authentication (this ...
To create a new wallet run the following in your terminal:
The above will output a short message of instruction, the path, and the seed to the screen.
You can read more about this command on its man page that can be accessed
via electrum help create.
There's a discussion on this with some answers here:
Cannot call rpc api from other machine in same local network
tl;dr: you need to also set the rpcbind setting to something like rpcbind=0.0.0.0 or rpcbind='ipaddress of node'. I needed to start the daemon with the -rpcbind=... option, it wouldn't work if I just set it in the conf file.
To expand on the answer from @Slavik Svyrydiuk : it only worked for me when starting the daemon with those options (-rpcbind=0.0.0.0 -rpcallowip=192.168.1.0/24).
If I set those in the conf and just started it like normal (sudo bitcoind -daemon) then it WOULD NOT open the port to external connections. It works only if I start the daemon with those settings ...
It depends on what you want.
If you want to know the amount of currency that has been available for miners to bring into circulation (the "210000-1 blocks of 50 BTC, then 210000 blocks of 25 BTC, then 210000 blocks of 12.5 BTC, ..." rule), the answer is no, there is no RPC that computes this. It's easy to do yourself, though.
If you want to compute ...
For anyone else finding this, and the problem was NOT a typo like in the accepted answer:
The issue for me was simply that I had my conf file in the wrong location.
I installed this on Ubuntu 20.04 and saved the conf file in /.bitcoin/bitcoin.conf, but it was looking in /home/user, which was actually ~.bitcoin/bitcoin.conf.
Saving the conf file in the ...