📅 Original date posted:2015-06-06
📝 Original message:Hi Kristov,
I like the idea. Mainly because having a standard reminds developers to consider this issue. In addition, we would have visibility into the portion of the network that adopts this strategy to enhance privacy. A few points of feedback:
- I think your explanation of sorting could be significantly shortened and clarified by simply saying that the TXIDs of inputs should be compared as uint256 integers.
- The malleability of input TXIDs, as mentioned in the proposal, could cause inputs to be ordered in a non-standard way. Reordering then them would invalidate the signatures (assuming SIGHASH_ALL), so the transaction would be left with improperly ordered inputs. While not a huge issue, it's not ideal. I think the best way to get around this would be to use normalized TXIDs, but you might also be able to sort based on the previous outputs that each of the inputs are spending? These both require information that may not be readily available, however, and use of normalized transaction IDs is not fully developed yet.
Best,
Stephen
> On Jun 5, 2015, at 8:12 PM, Kristov Atlas <kristovatlas.lists at gmail.com> wrote:
>
> Hello all,
>
> I have written a draft of a BIP to standardize the sorting of tx inputs and outputs for privacy and security reasons. A few colleagues have reviewed this and provided feedback privately, but now it's ready for feedback from a wider audience.
>
> If there is positive sentiment about the proposal after feedback is integrated, I aim for a bip number to be assigned and have it accepted into https://github.com/bitcoin/bips
>
> Link: https://github.com/kristovatlas/rfc/blob/master/bips/bip-li01.mediawiki
>
> For your convenience, here's the abstract:
>
> "Currently there is no standard for bitcoin wallet clients when ordering transaction inputs and outputs. As a result, wallet clients often have a discernible blockchain fingerprint, and can leak private information about their users. By contrast, a standard for non-deterministic sorting could be difficult to audit. This document proposes deterministic lexicographical sorting, using hashes of previous transactions and output indices to sort transaction inputs, as well as value and locking scripts to sort transaction outputs."
>
> Thanks,
>
> Kristov Atlas
> Open Bitcoin Privacy Project Contributor, Blockchain.info Security Engineer, etc.
> Twitter: @kristovatlas
> Blog: kristovatlas.com
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150605/6364f4b4/attachment.html>;
Stephen [ARCHIVE] /
npub1zq…53esn
2023-06-07 15:36:37
in reply to nevent1q…55pa
Author Public Key
npub1zq3c5mgvdpyvrt9evdtn48d47du4s03fxdjrvx7cv3mtf93hqjgqj53esnPublished at
2023-06-07 15:36:37Event JSON
{
"id": "9c497ec6edd31f4d28e60a88aefb65beaffc9e59c2aad10514640e923ecad224",
"pubkey": "10238a6d0c6848c1acb963573a9db5f379583e293364361bd86476b496370490",
"created_at": 1686152197,
"kind": 1,
"tags": [
[
"e",
"2ad30f0b7b1d9c682872004c147733c7f42d8c6ac9767498a41ff6a4eca5e892",
"",
"root"
],
[
"e",
"77c1aa836e86938d856dc56a075e688490c41bf37702088fef6e59fa7dc78fd4",
"",
"reply"
],
[
"p",
"e8c5be8658921444c6e1ceb34bd5fedce2326b4a65f72bb439a2d2b54f3fbb4b"
]
],
"content": "📅 Original date posted:2015-06-06\n📝 Original message:Hi Kristov,\n\nI like the idea. Mainly because having a standard reminds developers to consider this issue. In addition, we would have visibility into the portion of the network that adopts this strategy to enhance privacy. A few points of feedback:\n\n - I think your explanation of sorting could be significantly shortened and clarified by simply saying that the TXIDs of inputs should be compared as uint256 integers. \n - The malleability of input TXIDs, as mentioned in the proposal, could cause inputs to be ordered in a non-standard way. Reordering then them would invalidate the signatures (assuming SIGHASH_ALL), so the transaction would be left with improperly ordered inputs. While not a huge issue, it's not ideal. I think the best way to get around this would be to use normalized TXIDs, but you might also be able to sort based on the previous outputs that each of the inputs are spending? These both require information that may not be readily available, however, and use of normalized transaction IDs is not fully developed yet. \n\nBest,\nStephen \n\n\n\n\u003e On Jun 5, 2015, at 8:12 PM, Kristov Atlas \u003ckristovatlas.lists at gmail.com\u003e wrote:\n\u003e \n\u003e Hello all,\n\u003e \n\u003e I have written a draft of a BIP to standardize the sorting of tx inputs and outputs for privacy and security reasons. A few colleagues have reviewed this and provided feedback privately, but now it's ready for feedback from a wider audience.\n\u003e \n\u003e If there is positive sentiment about the proposal after feedback is integrated, I aim for a bip number to be assigned and have it accepted into https://github.com/bitcoin/bips \n\u003e \n\u003e Link: https://github.com/kristovatlas/rfc/blob/master/bips/bip-li01.mediawiki\n\u003e \n\u003e For your convenience, here's the abstract:\n\u003e \n\u003e \"Currently there is no standard for bitcoin wallet clients when ordering transaction inputs and outputs. As a result, wallet clients often have a discernible blockchain fingerprint, and can leak private information about their users. By contrast, a standard for non-deterministic sorting could be difficult to audit. This document proposes deterministic lexicographical sorting, using hashes of previous transactions and output indices to sort transaction inputs, as well as value and locking scripts to sort transaction outputs.\"\n\u003e \n\u003e Thanks,\n\u003e \n\u003e Kristov Atlas\n\u003e Open Bitcoin Privacy Project Contributor, Blockchain.info Security Engineer, etc.\n\u003e Twitter: @kristovatlas\n\u003e Blog: kristovatlas.com\n\u003e ------------------------------------------------------------------------------\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150605/6364f4b4/attachment.html\u003e",
"sig": "87c802e70274460ad1a2f1e2b29ee9bd50d511df909f35b5fd588d14f330a1a3cfd56ef0bb28acab66581d9aed0161bb7587d4bdacbab0689290ede3eb8b64c2"
}