Артём Литвинович [ARCHIVE] on Nostr: 📅 Original date posted:2018-01-24 📝 Original message:Greetings. I wanted to ask ...
📅 Original date posted:2018-01-24
📝 Original message:Greetings.
I wanted to ask what was the rationale behind still having both public
key and signature in Segwit witness?
As is known for a while, the public key can be derived from the
signature and a quadrant byte, a trick that is successfully used both
in Bitcoin message signing algorithm and in Ethereum transaction
signatures. The later in particular suggests that this is a perfectly
functional and secure alternative.
Leaving out the public key would have saved 33 bytes per signature,
which is quite a lot.
So, the question is - was there a good reason to do it the old way
(security, performance, privacy, something else?), or was it something
that haven't been thought of/considered at the time?
Published at
2023-06-07 18:10:15Event JSON
{
"id": "cad9595cda1cd48d155a6f5f085cb41411b366bba9801d8f9224d5791e6e9a93",
"pubkey": "42a88be9ef829076184e5a392761d358bd5fb4ed9ca07181809f9b3b5711915f",
"created_at": 1686161415,
"kind": 1,
"tags": [
[
"e",
"3f6c7b22fbffeeff2e300773ac429967bfcda0290cd9410855825712403ad534",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2018-01-24\n📝 Original message:Greetings.\n\nI wanted to ask what was the rationale behind still having both public\nkey and signature in Segwit witness?\n\nAs is known for a while, the public key can be derived from the\nsignature and a quadrant byte, a trick that is successfully used both\nin Bitcoin message signing algorithm and in Ethereum transaction\nsignatures. The later in particular suggests that this is a perfectly\nfunctional and secure alternative.\nLeaving out the public key would have saved 33 bytes per signature,\nwhich is quite a lot.\n\nSo, the question is - was there a good reason to do it the old way\n(security, performance, privacy, something else?), or was it something\nthat haven't been thought of/considered at the time?",
"sig": "5ad193834b32355952b107a79c893d785abc15696ce4be3694d13ae76bd92f6604dc2f6cebd536528320bf9c5f50860462138a4eab1c0560c0d32a419e16ab00"
}