Ruben de Vries [ARCHIVE] on Nostr: ๐
Original date posted:2015-01-14 ๐ Original message:For p2sh multisig TXs the ...
๐
Original date posted:2015-01-14
๐ Original message: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150114/9114f30a/attachment.html>
Published at
2023-06-07 15:28:29Event JSON
{
"id": "fe31ea2305461784d10a7b9f890d083546f13657fed8d101c8360d35dff5c267",
"pubkey": "e7bc665863fd1ca2200845ab536f9b5fa86c465fc4322ae11ce19b054512d50f",
"created_at": 1686151709,
"kind": 1,
"tags": [
[
"e",
"ef9480e99ea56d0362e9d11aa3d3348112e8c8b0adbfbdfee1624a1e22a745a8",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "๐
Original date posted:2015-01-14\n๐ Original message:For p2sh multisig TXs the order of the public keys affect the hash and\nthere doesn't seem to be an agreed upon way of sorting the public keys.\n\nIf there would be a standard (recommended) way of sorting the public keys\nthat would make it easier for services that implement some form of multisig\nto be compatible with each other without much hassle and making it possible\nto import keys from one service to another.\n\nI'm not suggesting forcing the order, just setting a standard to recommend,\nthere doesn't seem to be much reason for (new) services to not follow that\nrecommendation.\n\nRyan from BitPay broad this up before (\nhttps://sourceforge.net/p/bitcoin/mailman/message/32092958/) and in bitcore\nthey've implemented lexicographical sorting on the hex of the public key.\nIn a short search I can't find any other library that has a sorting\nfunction, let alone using it by default, so bitcore is currently my only\nreference.\n\n\nโRuben de Vries\nโCTO, BlockTrail\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150114/9114f30a/attachment.html\u003e",
"sig": "3dbdbc4c6df49f8d1856eeda373c84b3621517a32a89916af4bc4d4f669303731b94a07db44356123bfaa47a6d557febc5c6600624ab25356e5a1bca2de71c38"
}