📅 Original date posted:2019-01-22
📝 Original message:How could you prove the private key is in the burning transaction?
On Tue, Jan 22, 2019 at 11:56 AM Satoshin via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> This could could be a viable option. I think this is the right approach.
>
> Any downside to this and how much does this add to the blockweight if
> anything at all.
>
> Anonymouse
>
> > On Jan 22, 2019, at 4:19 AM, ZmnSCPxj via bitcoin-dev <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
> >
> > Good Morning Matt,
> >
> >> ### ZmnSCPxj,
> >>
> >> I'm intrigued by this mechanism of using fixed R values to prevent
> multiple signatures, but how do we derive the R values in a way where they
> are
> > unique for each blockheight but still can be used to create signatures
> or verify?
> >
> > One possibility is to derive `R` using standard hierarchical derivation.
> > Then require that the staking pubkey be revealed to the sidechain
> network as actually being `staking_pubkey = P + hash(P || parent_R) * G`
> (possibly with some trivial protection against Taproot).
> > To sign for a blockheight `h`, you must use your public key `P` and the
> specific `R` we get from hierarchical derivation from `parent_R` and the
> blockheight as index.
> >
> >
> >
> > Regards,
> > ZmnSCPxj
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
> _______________________________________________
> 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/20190122/46b08c8b/attachment-0001.html>;
Dustin Dettmer [ARCHIVE] /
npub1x5…kqsqu
2023-06-07 18:16:00
in reply to nevent1q…7zza
Author Public Key
npub1x54n25utwk7dzwzvk2v0aknptez5gxdwcyrxx2wgc0lnhgvwu72qmkqsquPublished at
2023-06-07 18:16:00Event JSON
{
"id": "b65444726baa1cdb0676c0b90733e0953371d154d996f2ef7cb84ec88b8b8a03",
"pubkey": "352b35538b75bcd1384cb298feda615e454419aec1066329c8c3ff3ba18ee794",
"created_at": 1686161760,
"kind": 1,
"tags": [
[
"e",
"4df79c01c3ed2b69e2412feaaaf51b7a98cb72fa692aaad7d28519466f8f3082",
"",
"root"
],
[
"e",
"aad4d47a20b40591517454ffe3ba413a195a254b28cb9aa3f8f31334fa574798",
"",
"reply"
],
[
"p",
"59f6bde20c9a2af7ea93b862d566b1cc0838b8641ba3ba88037658fcbd226938"
]
],
"content": "📅 Original date posted:2019-01-22\n📝 Original message:How could you prove the private key is in the burning transaction?\n\nOn Tue, Jan 22, 2019 at 11:56 AM Satoshin via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e This could could be a viable option. I think this is the right approach.\n\u003e\n\u003e Any downside to this and how much does this add to the blockweight if\n\u003e anything at all.\n\u003e\n\u003e Anonymouse\n\u003e\n\u003e \u003e On Jan 22, 2019, at 4:19 AM, ZmnSCPxj via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \u003e\n\u003e \u003e Good Morning Matt,\n\u003e \u003e\n\u003e \u003e\u003e ### ZmnSCPxj,\n\u003e \u003e\u003e\n\u003e \u003e\u003e I'm intrigued by this mechanism of using fixed R values to prevent\n\u003e multiple signatures, but how do we derive the R values in a way where they\n\u003e are\n\u003e \u003e unique for each blockheight but still can be used to create signatures\n\u003e or verify?\n\u003e \u003e\n\u003e \u003e One possibility is to derive `R` using standard hierarchical derivation.\n\u003e \u003e Then require that the staking pubkey be revealed to the sidechain\n\u003e network as actually being `staking_pubkey = P + hash(P || parent_R) * G`\n\u003e (possibly with some trivial protection against Taproot).\n\u003e \u003e To sign for a blockheight `h`, you must use your public key `P` and the\n\u003e specific `R` we get from hierarchical derivation from `parent_R` and the\n\u003e blockheight as index.\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e\n\u003e \u003e Regards,\n\u003e \u003e ZmnSCPxj\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190122/46b08c8b/attachment-0001.html\u003e",
"sig": "ae40db5ab29803ce2d9700787e252628a30b874e75409890c3debc136b359f005062197fb5d830b474b474b5429efb392f023b1b18c8a9f4cf2e22637710bf41"
}