đź“… Original date posted:2015-01-14
đź“ť Original message:At CryptoCorp we recommend to our customers that they sort
lexicographically by the public key bytes of the leaf public keys. i.e.
the same as BitPay.
On Wed, 2015-01-14 at 17:37 +0100, Ruben de Vries wrote:
> For p2sh multisig TXs the order of the public keys affect the hash and
> there doesn't seem to be an agreed upon way of sorting the public
> keys.
>
>
> If there would be a standard (recommended) way of sorting the public
> keys that would make it easier for services that implement some form
> of multisig to be compatible with each other without much hassle and
> making it possible to import keys from one service to another.
>
>
> I'm not suggesting forcing the order, just setting a standard to
> recommend, there doesn't seem to be much reason for (new) services to
> not follow that recommendation.
>
>
> Ryan from BitPay broad this up before
> (https://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in
> bitcore they've implemented lexicographical sorting on the hex of the
> public key.
> In a short search I can't find any other library that has a sorting
> function, let alone using it by default, so bitcore is currently my
> only reference.
>
>
>
>
> ​Ruben de Vries
> ​CTO, BlockTrail
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________ Bitcoin-development mailing list Bitcoin-development at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Miron / devrandom
devrandom [ARCHIVE] /
npub1a0…yuuph
2023-06-07 15:28:29
in reply to nevent1q…uatz
Author Public Key
npub1a04k8w0sg5trcey0tkz04maryv3q76yre2vqj8yrr4lfmf3m999qtyuuphPublished at
2023-06-07 15:28:29Event JSON
{
"id": "51fdd26315c7f0790cb3b486a25c10bbe2011ce2165a35c6e557095e45fbe1cf",
"pubkey": "ebeb63b9f045163c648f5d84faefa323220f6883ca98091c831d7e9da63b294a",
"created_at": 1686151709,
"kind": 1,
"tags": [
[
"e",
"ef9480e99ea56d0362e9d11aa3d3348112e8c8b0adbfbdfee1624a1e22a745a8",
"",
"root"
],
[
"e",
"fe31ea2305461784d10a7b9f890d083546f13657fed8d101c8360d35dff5c267",
"",
"reply"
],
[
"p",
"e7bc665863fd1ca2200845ab536f9b5fa86c465fc4322ae11ce19b054512d50f"
]
],
"content": "📅 Original date posted:2015-01-14\n📝 Original message:At CryptoCorp we recommend to our customers that they sort\nlexicographically by the public key bytes of the leaf public keys. i.e.\nthe same as BitPay.\n\nOn Wed, 2015-01-14 at 17:37 +0100, Ruben de Vries wrote:\n\u003e For p2sh multisig TXs the order of the public keys affect the hash and\n\u003e there doesn't seem to be an agreed upon way of sorting the public\n\u003e keys.\n\u003e \n\u003e \n\u003e If there would be a standard (recommended) way of sorting the public\n\u003e keys that would make it easier for services that implement some form\n\u003e of multisig to be compatible with each other without much hassle and\n\u003e making it possible to import keys from one service to another.\n\u003e \n\u003e \n\u003e I'm not suggesting forcing the order, just setting a standard to\n\u003e recommend, there doesn't seem to be much reason for (new) services to\n\u003e not follow that recommendation.\n\u003e \n\u003e \n\u003e Ryan from BitPay broad this up before\n\u003e (https://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in\n\u003e bitcore they've implemented lexicographical sorting on the hex of the\n\u003e public key.\n\u003e In a short search I can't find any other library that has a sorting\n\u003e function, let alone using it by default, so bitcore is currently my\n\u003e only reference.\n\u003e \n\u003e \n\u003e \n\u003e \n\u003e ​Ruben de Vries\n\u003e ​CTO, BlockTrail\n\u003e ------------------------------------------------------------------------------\n\u003e New Year. New Location. New Benefits. New Data Center in Ashburn, VA.\n\u003e GigeNET is offering a free month of service with a new server in Ashburn.\n\u003e Choose from 2 high performing configs, both with 100TB of bandwidth.\n\u003e Higher redundancy.Lower latency.Increased capacity.Completely compliant.\n\u003e http://p.sf.net/sfu/gigenet\n\u003e _______________________________________________ Bitcoin-development mailing list Bitcoin-development at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\n-- \nMiron / devrandom",
"sig": "bcbb2346ff47c5996ba989669b7eefa432f8095266fa98ccf762f6de721b1bff9f043113c42f46eed9fec0c11fbfca0b7b00f34d4d0dca0250ad9639b7891b92"
}