clashicly
commented
6 years ago It seems clashic-qt is able to connect to nodes running on port 8333 But clashicd seems to only try to connect to port 10333 when retrieving nodes from Bitcoin Cash seeders
# tail -f debug.log 2018-04-30 17:37:44 connect() to 128.199.164.172:10333 failed after select(): Connection refused (111) 2018-04-30 17:37:51 connect() to 46.4.33.85:10333 failed after select(): Connection refused (111) 2018-04-30 17:37:57 connect() to 192.203.228.91:10333 failed after select(): Connection refused (111) 2018-04-30 17:37:57 connect() to 45.63.39.112:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:03 connect() to 195.154.177.49:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:10 connect() to 47.95.32.168:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:10 connect() to 47.94.47.209:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:22 connect() to 47.94.45.184:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:22 connect() to 192.187.121.43:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:28 connect() to 199.101.100.58:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:40 connect() to 54.36.176.224:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:41 connect() to 172.104.151.66:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:41 connect() to 192.99.19.160:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:42 connect() to 45.77.43.164:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:43 connect() to 67.221.142.252:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:43 connect() to 206.51.235.198:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:44 connect() to 47.88.57.99:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:44 connect() to 138.197.160.144:10333 failed after select(): Connection refused (111) 2018-04-30 17:38:50 connect() to 109.233.58.46:10333 failed after select(): No route to host (113)
Therefore it gets no blocks
# clashic-cli -rpcconnect=127.0.0.1 -rpcport=10332 -rpcuser=somerpcuser -rpcpassword=somerpcpassword getblockchaininfo { "chain": "main", "blocks": 0, "headers": 0, "bestblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f", "difficulty": 1, "mediantime": 1231006505, "verificationprogress": 3.147261566546461e-09, "chainwork": "0000000000000000000000000000000000000000000000000000000100010001", "pruned": true, "softforks": [ { "id": "bip34", "version": 2, "reject": { "status": false } }, { "id": "bip66", "version": 3, "reject": { "status": false } }, { "id": "bip65", "version": 4, "reject": { "status": false } } ], "bip9_softforks": { "csv": { "status": "defined", "startTime": 1462060800, "timeout": 1493596800, "since": 0 } }, "pruneheight": 0 }
only way to jumpstart is explicitly adding via clashic-cli
# clashic-cli -rpcconnect=127.0.0.1 -rpcport=10332 -rpcuser=somerpcuser -rpcpassword=somerpcpassword addnode xxx.xxx.xxx.xxx:8333 add
Then the debug.log starts flooding in
2018-04-30 18:00:08 UpdateTip: new best=000000001786abd75dc912d8eabe85080c7e822858d445644fa3a3e059c2033b height=51729 version=0x00000001 log2_work=48.571264 tx=53868 date='2010-04-18 18:14:28' progress=0.000170 cache=10.8MiB(53381txo) 2018-04-30 18:00:08 UpdateTip: new best=000000001e4405ae38eeedceafcced6e8108d2c63f07999b26026d2e16e9f5b2 height=51730 version=0x00000001 log2_work=48.57138 tx=53982 date='2010-04-18 18:19:38' progress=0.000170 cache=10.8MiB(53494txo) 2018-04-30 18:00:08 UpdateTip: new best=00000000071ca88b41fe390be49c489b325aab404605bca51c0c499ad824cdfb height=51731 version=0x00000001 log2_work=48.571496 tx=54070 date='2010-04-18 18:28:28' progress=0.000170 cache=10.8MiB(53582txo) 2018-04-30 18:00:08 UpdateTip: new best=0000000008c5ebcd04a8303c6c35c84e0560ef5a3e1ca34c59e356216eecc4c8 height=51732 version=0x00000001 log2_work=48.571612 tx=54073 date='2010-04-18 18:29:17' progress=0.000170 cache=10.8MiB(53585txo) 2018-04-30 18:00:08 UpdateTip: new best=000000001df6a4e1a1634ac4bf11a80a7444ee1f0b46543c22a827fdfb12b559 height=51733 version=0x00000001 log2_work=48.571728 tx=54092 date='2010-04-18 18:29:16' progress=0.000170 cache=10.8MiB(53604txo) 2018-04-30 18:00:08 UpdateTip: new best=00000000042a3aee0691a8705cf96536e8ad71b01a3deddb82e1ebc1c4540053 height=51734 version=0x00000001 log2_work=48.571843 tx=54491 date='2010-04-18 18:32:21' progress=0.000171 cache=10.9MiB(54002txo) 2018-04-30 18:00:08 UpdateTip: new best=000000001314b2b56784f69bedc782a858bff9909f495a3c06066f865b092f1a height=51735 version=0x00000001 log2_work=48.571959 tx=54654 date='2010-04-18 18:36:33' progress=0.000172 cache=10.9MiB(54165txo) 2018-04-30 18:00:08 UpdateTip: new best=0000000006cb0e1cdd14238e8b55140c0e743ea11e9479d029e48bb63175ce30 height=51736 version=0x00000001 log2_work=48.572075 tx=54674 date='2010-04-18 18:38:04' progress=0.000172 cache=10.9MiB(54185txo)
cryptomeow
Started branch as 0.15.101, but on User Agent it came up at 0.16.1. Fixed the issue with versioning. So it shall be Bitcoin Clashic ABCD 0.16.1
This is the sum total of Rebranding. This client is designed to run side by side with Bitcoin Core, Bitcoin ABC, Litecoin core, etc.
It does not contain consensus changes. No hardfork in this pull request.