Back to Topic
Never a dull moment on the blockchain:
<img src="https://imgur.com/wGYDhbvl.png" />
A few notes on the logfiles output by BCHD:
...from peer 184.108.40.206:8333 (outbound), code: REJECT_NONSTANDARD, reason: bad-txns-nonfinal
2020-06-06 01:00:34.222 [WRN] PEER: Received reject message from peer 220.127.116.11: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
New BCHD release! update in time for the fork :) https://github.com/gcash/bchd/releases/tag/v0.16.0
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 18.104.22.168:56152 (inbound) (neutrino:0.0.4-beta/)
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 22.214.171.124:41186 (inbound) (/bcoinsv:1.1.0/)
How to hack BCHD v0.14.0 to accept OP_RETURN transactions:
[email protected]:~/Progs$ ipfs add BCHD+OP_RETURN.hack.tar.gz
added QmPF3P7NY2Dabkdn9i3BS49eaiYNaKqMc31ajzpdsNRNwW BCHD+OP_RETURN.hack.tar.gz
Sadly(®) BCHD 0.14.0 still rejects MEMO protocol transactions.
I will revisit the process of recoding the source to avoid this flaw.
Update on the IFPS side of things:
after repeated failures of the downloaded UTXO
disabling the IPFS and trying BCHD --fastsync again seems to run smooth.
perhaps I misconfigured the IPFS. yuk
Problems with OP_RETURN are no longer a mystery.
The original BTCD was written in a savagely rabid "THOU SHALT NOT USE OP_RETURN EVER !#!" manner.
Lots of logic flaws exist but these are easy.
BCHD --fastsync option makes reloading a borked instance easy.
However, bchd crashes at 2gb limit on IPFS fastsync.
fix = "pin add" the utxo data so it loads internally instead of over the wire.