From: Satoshin <satoshin@mybitcoincenter•com>
To: ZmnSCPxj <ZmnSCPxj@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proof-of-Stake Bitcoin Sidechains
Date: Tue, 22 Jan 2019 09:58:25 -0500 [thread overview]
Message-ID: <9D2883DC-360C-401A-B518-B8205A3AAA53@mybitcoincenter.com> (raw)
In-Reply-To: <wTXHV7W_AXHz5xdhXJVJr2OdSpEOaFh0PBQubFdZv4JyF6SlImszj2QyF9G-_Dem06A3iBWLF3vdgiHC_NlsVqy7DFX5XTphajNnMqiU6r0=@protonmail.com>
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@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@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2019-01-22 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:59 Matt Bell
2019-01-19 1:42 ` ZmnSCPxj
2019-01-19 5:35 ` Matt Bell
2019-01-20 2:06 ` ZmnSCPxj
2019-01-21 18:47 ` Matt Bell
2019-01-22 9:19 ` ZmnSCPxj
2019-01-22 14:58 ` Satoshin [this message]
2019-01-22 20:03 ` Dustin Dettmer
2019-01-22 16:33 ` Dustin Dettmer
2019-01-24 10:03 ` ZmnSCPxj
2019-01-24 18:46 ` Matt Bell
2019-01-25 0:16 ` Peter Todd
2019-01-25 5:33 ` ZmnSCPxj
2019-01-22 20:22 ` Dr Adam Back
2019-02-01 9:19 ` ZmnSCPxj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D2883DC-360C-401A-B518-B8205A3AAA53@mybitcoincenter.com \
--to=satoshin@mybitcoincenter$(echo .)com \
--cc=ZmnSCPxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox