114d
The golang bitcoin-cash node software that has "fast-sync":
https://github.com/gcash/bchd
https://bchd.cash/
  114d
Works - now I want to explore how to firehose real-time TX data into a file.
  114d
BCHD is written in Google Go Language, which is a pretty impressive but not overly verbose.
  93d
Getting txdata remains a chore, resembles pulling teeth more than filling a bucket.
  83d
Okay - so I finally got TXIDs streaming out of my beautiful BCHD node
  83d
And then in deepest despair I begin to realize it religiously abandons almost all the op_returns from Memo
  83d
I am not sure yet if BCHD simply rejects them
or if it just never sees them (network?)
but this is tragic
BCHd has everything I wanted in a node: IPFS + GO and more.
but no Memo data.
  82d
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.
  81d
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
  75d
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.
  72d
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
  34d
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.
  34d
  34d
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.
  28d
Sadly(®) BCHD 0.14.0 still rejects MEMO protocol transactions.
I will revisit the process of recoding the source to avoid this flaw.
  25d
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
  7d
2019-04-18 19:19:14.127 [INF] SYNC: New valid peer 139.162.198.175:41186 (inbound) (/bcoinsv:1.1.0/)
  5d
Got some videos for ya's.
  5d
&t=
  5d
  2d
and v0.14.2 does accept OP_RETURN transactions.
This means it is immediately useful for MEMO protocol operations,
Thanks to the BCHD team