The-One-Law_Sanctuary
47 days ago
The golang bitcoin-cash node software that has "fast-sync":
https://github.com/gcash/bchd
https://bchd.cash/
The-One-Law_Sanctuary
47 days ago
Works - now I want to explore how to firehose real-time TX data into a file.
CockBlockstream
46 days ago
BCHD is written in Google Go Language, which is a pretty impressive but not overly verbose.
The-One-Law_Sanctuary
26 days ago
Getting txdata remains a chore, resembles pulling teeth more than filling a bucket.
The-One-Law_Sanctuary
16 days ago
Okay - so I finally got TXIDs streaming out of my beautiful BCHD node
The-One-Law_Sanctuary
16 days ago
And then in deepest despair I begin to realize it religiously abandons almost all the op_returns from Memo
The-One-Law_Sanctuary
16 days ago
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.
The-One-Law_Sanctuary
15 days ago
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.
The-One-Law_Sanctuary
14 days ago
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
The-One-Law_Sanctuary
8 days ago
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.
The-One-Law_Sanctuary
5 days ago
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