From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proof-of-Stake Bitcoin Sidechains
Date: Fri, 25 Jan 2019 05:33:37 +0000 [thread overview]
Message-ID: <Bug73hgjU4TRIBFN5mQOLITGwsT5nHcr4J4ssOL2qXcLVh-GHClWYNm6UK-snj9uJFrVrcW2OQWZ94DhzukauNp-L1jk53p0J6WbekbKvpQ=@protonmail.com> (raw)
In-Reply-To: <23C4B29C-0A0C-4680-BF99-3A86C215BE34@petertodd.org>
Good mornint Peter,
> > > Wouldn’t a revealed private key for time locked funds create a race
> > > to spend? I imagine miners who are paying attention would have the
> > > advantage but it would still just be a race.
> >
> > If Bitcoin had implemented RBF "properly" (i.e. not have the silly
> > "opt-out" rule) then such races are won by bidding up the fees. A
>
> Note that CSV using transactions are always RBF as CSV disables the opt-out.
>
Thank you for this information.
I forgot that RBF opt-out was hacked on top of `nSequence`, and relative timelocks were also hacked on top of `nSequence`.
In particular coins locked on mainchain for the purpose of staking a sidechain (mainstake) have to be locked with an `OP_CSV`, which immediately enables this protection.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2019-01-25 5:33 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
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 [this message]
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='Bug73hgjU4TRIBFN5mQOLITGwsT5nHcr4J4ssOL2qXcLVh-GHClWYNm6UK-snj9uJFrVrcW2OQWZ94DhzukauNp-L1jk53p0J6WbekbKvpQ=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pete@petertodd$(echo .)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