458d
You can test nodes here:
(require.patience): https://cash.coin.dance/nodes#nodeChecker
2019-05-06 12:24:06.346 [INF] SYNC: New valid peer 34.218.174.49:44678 (inbound) (/bitnodes.coin.dance:0.1/)
444d
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.
434d
Which blockchain is this ?!
434d
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)
393d
New BCHD Website! More information about the node implementation & the Neutrino Wallet https://bchd.cash - https://www.reddit.com/r/btc/comments/cb07ve/bchd_new_website_with_a_lot_more_information/
354d
BCHwallet
Anyone out there using this ?
https://github.com/gcash/bchwallet
Any advice regarding this would be welcome here...
350d
329d
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
302d
Who wants some $BCHD tokens?
288d
238d
BCHD is now available on the AUR for Arch / Manjaro users https://aur.archlinux.org/packages/bchd/
233d
You can now run a Member server off your own BCHD node! https://github.com/memberapp/server
93d
OUCH: ☠
TXid output 1eda05622b2f5ce509f396118087e78caceb3d76efc3cb03d142961db3ee2bc9:1 referenced from transaction 000bf24801c9ca1dc8e4e22a20f249601ebdeb8881c7f8aedefbcbdde71f709e:0 does not exist
92d
New BCHD release! update in time for the fork :) https://github.com/gcash/bchd/releases/tag/v0.16.0
91d
BCHD needs funding. Their Flipstarter fundraiser only has 3 days left!

https://bchd.flipstarter.cash/
91d
This easy guide shows how to pledge for a FlipStarter funding campaign!

https://read.cash/@flipstarter/how-to-support-a-flipstarter-campaign-f27240d9
89d
BCHD reached their flipstarter goal! Congrats!
74d
74d
Apparently,
when BCHD misplaces something ephemeral,
the full-node system needs to be reSYNCed from zero.
This is the second time I have seen it.
Time wasted reSYNCing a full node is insane.
67d
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
61d
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...
60d
A few notes on the logfiles output by BCHD:
42d
40d
Never a dull moment on the blockchain:
<a href="
<img src=" />
</a>
30d
10d