Test raising the maxorphantx to 8095 to try and avoid any more trainwrecks

https://i.imgur.com/VKUFRyo.png Woot woot fasten your seatbelts

https://i.imgur.com/qB3tJwU.png a rather curious block number sequence... .. . .. ....

https://github.com/gcash/bchd/releases/tag/v0.17.0

https://i.imgur.com/0QM6TYZ.png fun while it lasted, hope it does not do this during the fork.

bchd v0.16.5 is out: https://github.com/gcash/bchd/releases/tag/v0.16.5

Never a dull moment on the blockchain: <a href="https://i.imgur.com/wGYDhbv.png"> <img src="https://imgur.com/wGYDhbvl.png" /> </a>

A few notes on the logfiles output by BCHD:

More fun: ...from peer 18.195.144.149:8333 (outbound), code: REJECT_NONSTANDARD, reason: bad-txns-nonfinal 2020-06-06 01:00:34.222 [WRN] PEER: Received reject message from peer 120.79.238.24:8333...

Apparently BCHCTL can quit working permanently: ":~$ bchctl getinfo Post "https://localhost:8334": dial tcp [::1]:8334: connect: connection refused" even if rpcuser/pass matches both .conf files

https://i.imgur.com/K4fykOW.png

New BCHD release! update in time for the fork :) https://github.com/gcash/bchd/releases/tag/v0.16.0

OUCH: ☠ TXid output 1eda05622b2f5ce509f396118087e78caceb3d76efc3cb03d142961db3ee2bc9:1 referenced from transaction 000bf24801c9ca1dc8e4e22a20f249601ebdeb8881c7f8aedefbcbdde71f709e:0 does not exist

Reboot + reSync + full tx index + full address index ...wondering how long this would take on one of those legendary Arm nodes... 2019-09-12 06:07:58.980 [INF] BCHD: Version 0.14.7

BCHD is now available on the AUR for Arch / Manjaro users https://aur.archlinux.org/packages/bchd/

bchd 0.15.0 is out https://reddit.com/r/btc/comments/dli31q/bchd_0150_released_with_nov_hardfork_compatibility/

Who wants some $BCHD tokens?

New BCHD release! https://github.com/gcash/bchd/releases/tag/v0.14.7

Which blockchain =812484 blocks ?! 2019-05-30 03:50:27.745 [INF] SYNC: Processed 2 blocks in 10.32s (4496 transactions, height 422369/812484 (51.98%), 2016-07-26 17:46:53 +0000 UTC, ~105 MiB cache)

SIGSEGV crash appears unrecoverable on BCHD, Lacks any CLI methods to roll back and reSYNC Restart SYNC taking weeks puts this out of reach on v0.14.3 at this time. Parked, awaiting next release.

2019-05-06 12:18:04.370 [INF] SYNC: New valid peer 196.249.98.94:56152 (inbound) (neutrino:0.0.4-beta/)

https://github.com/gcash/bchd/releases/tag/v0.14.3 Upgrade from 0.14.2 (mid-SYNC) was painless. Now awaiting the 100% SYNCed moment v0.14.3 has features to investigate once fully SYNCed.

Just a note on what spooling up a full v0.14.2 node entails: 2cores 8gb

2019-04-18 19:19:14.127 [INF] SYNC: New valid peer 139.162.198.175:41186 (inbound) (/bcoinsv:1.1.0/)

How to hack BCHD v0.14.0 to accept OP_RETURN transactions: ipfs@test:~/Progs$ ipfs add BCHD+OP_RETURN.hack.tar.gz added QmPF3P7NY2Dabkdn9i3BS49eaiYNaKqMc31ajzpdsNRNwW BCHD+OP_RETURN.hack.tar.gz