Topic - BCHD

Back to topics Threads View 7 followers

  253d
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.
  252d
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
  246d
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.
  243d
I see a new BCHD peer
104.248.209.144 (/bchd:0.13.0(EB32.0)/)
seems to have go online and is rejecting OP_RETURN transactions
I have fixed it in the code I am using and am almost ready to share
  205d
I see Chris just released 0.14.0 a few hours ago (Thanks Chris)
so I guess I will be spending time
seeing if it still discards OP_RETURN.
Even if it does
I will simply recode it anyway.
  205d
https://github.com/gcash/bchd/releases/tag/v0.14.0
  205d
Hopefully helpful hint deartment:
If you try to run both IPFS and BCHD
on an under-powered server ,
start IPFS first
and then start BCHD
so cpu and mem usage stays sane.
  199d
Sadly(®) BCHD 0.14.0 still rejects MEMO protocol transactions.
I will revisit the process of recoding the source to avoid this flaw.
  196d
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
  178d
2019-04-18 19:19:14.127 [INF] SYNC: New valid peer 139.162.198.175:41186 (inbound) (/bcoinsv:1.1.0/)
  176d
Got some videos for ya's.
  176d
&t=
  176d
Also, BCHD 0.14.2 is out! https://github.com/gcash/bchd/releases/tag/v0.14.2
  173d
and v0.14.2 does accept OP_RETURN transactions.
This means it is immediately useful for MEMO protocol operations,
Thanks to the BCHD team
  170d
Just a note on what spooling up a full v0.14.2 node entails: 2cores 8gb
  161d
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.
  160d
2019-05-06 12:18:04.370 [INF] SYNC: New valid peer 196.249.98.94:56152 (inbound) (neutrino:0.0.4-beta/)
  160d
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/)
  146d
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.
  136d
Which blockchain is this ?!
  136d
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)
  96d
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/
  56d
BCHwallet
Anyone out there using this ?
https://github.com/gcash/bchwallet
Any advice regarding this would be welcome here...
  52d
New BCHD release! https://github.com/gcash/bchd/releases/tag/v0.14.7
  31d
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
  5d
Who wants some $BCHD tokens?

About Blog Disclaimer Stats