📅 Original date posted:2015-01-14
📝 Original message:I think everyone is pretty much following this standard now.
- Eric
On Jan 14, 2015 12:58 PM, "devrandom" <c1.sf-bitcoin at niftybox.net> wrote:
> 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
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150114/230bd912/attachment.html>;
Eric Lombrozo [ARCHIVE] /
npub1az…t2krq
2023-06-07 17:28:30
in reply to nevent1q…ymjg
Author Public Key
npub1azvhdrf9fu6n0tm7yez4j6zcxcedp2ct6nrcq3z74naqs7kgpk8s5t2krqPublished at
2023-06-07 17:28:30Event JSON
{
"id": "5ce987fa7780a3352933365e39e88225d2d7df4789f585af334a3bf52b220662",
"pubkey": "e899768d254f3537af7e26455968583632d0ab0bd4c780445eacfa087ac80d8f",
"created_at": 1686151710,
"kind": 1,
"tags": [
[
"e",
"ef9480e99ea56d0362e9d11aa3d3348112e8c8b0adbfbdfee1624a1e22a745a8",
"",
"root"
],
[
"e",
"51fdd26315c7f0790cb3b486a25c10bbe2011ce2165a35c6e557095e45fbe1cf",
"",
"reply"
],
[
"p",
"ebeb63b9f045163c648f5d84faefa323220f6883ca98091c831d7e9da63b294a"
]
],
"content": "📅 Original date posted:2015-01-14\n📝 Original message:I think everyone is pretty much following this standard now.\n\n- Eric\nOn Jan 14, 2015 12:58 PM, \"devrandom\" \u003cc1.sf-bitcoin at niftybox.net\u003e wrote:\n\n\u003e At CryptoCorp we recommend to our customers that they sort\n\u003e lexicographically by the public key bytes of the leaf public keys. i.e.\n\u003e the same as BitPay.\n\u003e\n\u003e On Wed, 2015-01-14 at 17:37 +0100, Ruben de Vries wrote:\n\u003e \u003e For p2sh multisig TXs the order of the public keys affect the hash and\n\u003e \u003e there doesn't seem to be an agreed upon way of sorting the public\n\u003e \u003e keys.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e If there would be a standard (recommended) way of sorting the public\n\u003e \u003e keys that would make it easier for services that implement some form\n\u003e \u003e of multisig to be compatible with each other without much hassle and\n\u003e \u003e making it possible to import keys from one service to another.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e I'm not suggesting forcing the order, just setting a standard to\n\u003e \u003e recommend, there doesn't seem to be much reason for (new) services to\n\u003e \u003e not follow that recommendation.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e Ryan from BitPay broad this up before\n\u003e \u003e (https://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in\n\u003e \u003e bitcore they've implemented lexicographical sorting on the hex of the\n\u003e \u003e public key.\n\u003e \u003e In a short search I can't find any other library that has a sorting\n\u003e \u003e function, let alone using it by default, so bitcore is currently my\n\u003e \u003e only reference.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e Ruben de Vries\n\u003e \u003e CTO, BlockTrail\n\u003e \u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \u003e New Year. New Location. New Benefits. New Data Center in Ashburn, VA.\n\u003e \u003e GigeNET is offering a free month of service with a new server in Ashburn.\n\u003e \u003e Choose from 2 high performing configs, both with 100TB of bandwidth.\n\u003e \u003e Higher redundancy.Lower latency.Increased capacity.Completely compliant.\n\u003e \u003e http://p.sf.net/sfu/gigenet\n\u003e \u003e _______________________________________________ Bitcoin-development\n\u003e mailing list Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e --\n\u003e Miron / devrandom\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\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 _______________________________________________\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\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150114/230bd912/attachment.html\u003e",
"sig": "d955df8c0fa1445952f24e4ff9f41daa6321144f4f77a9d4d08840cb64a37d779cd850155411a189e95a4cdb084a05f23cdc678d12a7f98a23d152e9c40d9319"
}