Kristov Atlas [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2014-04-23 to 2016-05-19
💬 Posted a total of 28 messages
📚 Participated in the following categories: Bitcoin-development, RFC, bitcoin-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 17:41:25

- reply

📅 Original date posted:2015-07-01
📝 Original message:Hi Justus,
What are the potential applications for this BIP?
-Kr
On Jun 30, 2015 1:53 PM, "Justus Ranvier" <justus.ranvier at monetas.net>
wrote:
> Monetas has developed a Bitmessage address derivation method from an
> HD seed based on BIP-43.
>
>
> https://github.com/monetas/bips/blob/bitmessage/bip-bm01.mediawiki
>
>
> We're proposing this as a BIP per the BIP-43 recommendation in order
> to reserve a purpose code.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150701/8418af96/attachment.html>

2023-06-07 17:36:36

- reply

📅 Original date posted:2015-06-05
📝 Original message: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150605/9ba7bf54/attachment.html>