Op Ed: Three Technical Requirements to Connect Blockchains Without a Token (bitcoinmagazine.com)

In my last post, I was talking about how connecting all blockchains is the final stepping stone for mass-crypto adoption. Here I want to outline the technical building blocks with which this idea can be implemented.Since I see a lot of downsides to having one large uber-blockchain connecting all others, I will focus on a token-LESS solution. This would have several advantages:No…

Bitcoin

bitcoin-cli – “error: couldn’t connect to server” –

I have bitcoind 0.13.1 running on a Raspberry Pi. I can see it on the bitcoin network using bitnodes.21.co but I can’t connect to it locally with bitcoin-cli.

My bitcoin.conf is:

rpcuser=xxx rpcpassword=xxx listen=1 server=1 dbcache=50 daemon=1 testnet=0 maxuploadtarget=200 

I tried:

curl --user xxx --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' 127.0.0.1:8332

and I got:

curl: (7) Failed to connect to 127.0.0.1 port 8332: Connection refused

Netstat:

sudo netstat -tulpn | grep bitcoin

gives:

tcp        0      0 0.0.0.0:8333            0.0.0.0:*               LISTEN      620/bitcoind     tcp6       0      0 ::1:8332                :::*                    LISTEN      620/bitcoind     tcp6       0      0 :::8333                 :::*                    LISTEN      620/bitcoind' 

I had a crash a couple of days ago and had to recover wallet.dat from a backup. After the crash the time on the pi was an hour slow. I had to stop and start ntp to get it correct. I also did an apt-get update and upgrade after the crash. Until the crash this worked fine.

Finally I see that all the files in the dataDir are executable by everyone. The dataDir is on a USB stick that is mounted with:

/dev/sda1 /home/pi/bitcoinData vfat uid=pi,gid=pi,umask=0022,sync,auto,nosuid,rw,nouser 0 0

I am tempted to start over but would really like to understand why this has stopped working.

Recent Questions – Bitcoin Stack Exchange