Dagur Valberg
Dagur Valberg
This is neat. Is it possible for me or others to add to the bounty? Why not have a permanent address in this issue?
Sounds good to me. Return tip after n days of issue being closed if it isn’t reopened. Most importantly remove it from the open bounties list so no one begins...
The `validaterawtransaction` is very detailed, the full API is response is [here](https://gitlab.com/bitcoinunlimited/BCHUnlimited/-/blob/dev/src/rpc/rawtransaction.cpp#L1529). If it's a superset of `testmempoolaccept`, then we could at least support what they have in common.
While it would be interesting, * Double spends on BTC are not relayed and I would need custom software that connects to lots of nodes to to semi-reliably detect them....
> The business I work for is processing relatively large BTC transactions with zero conf, so yes we do care. That is very interesting. I too do care, which is...
I'd love to hear your ideas about mitigating risk @Transisto
I want this as a feature in XT, I created an issue for it here: https://github.com/bitcoinxt/bitcoinxt/issues/462
Would creating a static _index of all double spends_ allow you create the statistics you're after? For example `txdata/index.json` with array of ``` { 'firstseen' : timestamp, 'tx1' : txid,...
I'll forward your tip into a bounty :-) **Bounty: Create an index as described in comment above.** @chaintip 180 days