New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

idea: conflicting transaction ids #398

Open

braydonf opened this issue Oct 9, 2015 · 1 comment

Labels

feature request

Contributor

braydonf commented Oct 9, 2015

Add "conflictingTxIds" where there was previously "doubleSpentTxId" and the value would be an array of transactions that have been seen in the network to conflict.
Add the same field to unspent outputs for an address, so that clients can filter these transactions when selecting outputs to spend.

braydonf mentioned this issue

Add a mempool only index with conflicting txids bitpay/bitcore-node#304

Closed

Contributor

isocolsky commented Oct 9, 2015

Just a note about this: the conflictingTxs array should have elements of the form { txid: ..., index: ... }, at least in the case of utxos.

braydonf changed the title ~~v0.3.0+ conflicting transaction ids~~ idea: conflicting transaction ids

braydonf added the feature request label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment