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

v0.13.1 wallet – connect failed: Network is unreachable (101)

Noob here. Ran the core wallet on my Linux PC and looking for help as to why it is not working after syncing up the history of blockchain Tx’s. Is this likely my router not passing port 8333 packets, or something else? thanks!

2016-12-15 13:39:52 Pre-allocating up to position 0xe00000 in rev00709.dat 2016-12-15 13:39:52 UpdateTip: new best=0000000000000000021ab2f093924ee05d43c228c2f6ab84414d7b77bef0ca18 height=443582 version=0x20000000 log2_work=85.680045 tx=179248787 date='2016-12-15 13:40:26' progress=1.000000 cache=175.8MiB(93812tx) warning='2 of last 100 blocks have unexpected version' 2016-12-15 13:39:54 ProcessMessages: advertising address 179.125.21.234:8333 2016-12-15 13:39:54 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443582, us=179.125.21.234:58800, peer=21 2016-12-15 13:39:54 AdvertiseLocal: advertising address 179.125.21.234:8333 2016-12-15 13:41:31 connect() to [2001:0:9d38:6ab8:3c33:1df8:ab64:a421]:8333 failed: Network is unreachable (101) 2016-12-15 13:41:59 connect() to 114.254.131.229:8333 failed after select(): Connection refused (111) 2016-12-15 13:43:00 connect() to [2001:0:9d38:6ab8:249a:276e:a1e9:fc4b]:8333 failed: Network is unreachable (101) 2016-12-15 13:46:38 connect() to [2001:0:9d38:90d7:2068:fbff:2776:17b5]:8333 failed: Network is unreachable (101) 2016-12-15 13:48:46 connect() to [2001:0:5ef5:79fd:344e:fda:b3e8:2a0d]:8333 failed: Network is unreachable (101) 2016-12-15 13:53:08 ProcessMessages: advertising address 179.125.21.234:8333 2016-12-15 13:53:08 receive version message: /Satoshi:0.13.1/: version 70014, blocks=443582, us=179.125.21.234:48796, peer=22 2016-12-15 13:53:08 AdvertiseLocal: advertising address 179.125.21.234:8333 2016-12-15 13:53:25 UpdateTip: new best=0000000000000000004cfce5b4e88c754daa10165a2495fbc9893a8fb054f938 height=443583 version=0x30000000 log2_work=85.680076 tx=179251601 date='2016-12-15 13:53:36' progress=1.000000 cache=217.3MiB(104890tx) warning='3 of last 100 blocks have unexpected version' 

Recent Questions – Bitcoin Stack Exchange

How to let a peer connect to a peer’s peer?

I’m testing a new altcoin that I’ve created between several computers in LAN but encounter a situation as follow:

Computer A’s client connects to computer B’s client through the B’s IP in the addnode field in the config file and only B’s IP is specified in it. The same thing happens between B and C as C only knows B through the config file. It seems that there is no connection between A and C since the the command getpeerinfo in both A and C doesn’t show the other’s IP. Indeed, when I shut down the client on computer B, the two clients on A and C become disconnected to the network.

So my question is: what should I do to make A and C connected since they share a common peer’s connection? (assuming that the new common connections are random, not known in advance to be included in the config file)

I’ve read somewhere that there are seed nodes which stores IPs of clients which have connected to them and that they usually don’t need to keep connecting to those new nodes, just save the addresses in the database and disconnect. In case of new peer connects to the network, those seed nodes will help to provide list of peers’ IPs. So how can I configure a node to be a seed node? Is it in this case the DNS seed? (I guess it’s not)

Thank you in advance and all kinds of help will be highly appreciated.

Recent Questions – Bitcoin Stack Exchange

Where to connect to get streaming blockchain data?

I would like to connect to the blockchain to read the whole thing, then listen to it “live” as it streams.

I’m new to this and can’t seem to find out how to connect to receive data. (is there a central server, is it peer to peer…)

Is it a push or pull type of format? ie: Do I need to setup and endpoint and register to get the stream, or do I need to poll something?

Again new to this, any help would be appreciated.

Recent Questions – Bitcoin Stack Exchange