public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kekcoin <kekcoin@protonmail.com>
To: Tao Effect <contact@taoeffect.com>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>,
	Anthony Towns <aj@erisian.com.au>
Subject: Re: [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable
Date: Tue, 06 Jun 2017 20:19:18 -0400	[thread overview]
Message-ID: <oSkyoMQ0QQadP3ZDrIU_Xw0sEG8lv5q3B5Kjwnu_MIkvUGmg9TrDn1myLeRhPhyPpGbAgp1QWkerbp76jjptWhh4jz3JXjVycXuXZkxodG8=@protonmail.com> (raw)
In-Reply-To: <78F1D626-0D38-48FD-B2AF-378765182751@taoeffect.com>

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

Hmm, that's not the difference I was talking about. I was referring to the fact that using "post-chainsplit coinbases from the non-148 chain" to unilaterally (ie. can be done without action on the 148-chain) taint coins is more secure in extreme-adverserial cases such as secret-mining reorg attacks (as unfeasibly expensive they may be); the only large-scale (>100 block) reorganization the non-148 chain faces should be a resolution of the chainsplit and therefore render the replay threat moot.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

-------- Original Message --------
Subject: Re: [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable
Local Time: June 7, 2017 3:04 AM
UTC Time: June 7, 2017 12:04 AM
From: contact@taoeffect.com
To: Kekcoin <kekcoin@protonmail.com>
Anthony Towns <aj@erisian.com.au>, bitcoin-dev@lists.linuxfoundation.org <bitcoin-dev@lists.linuxfoundation.org>

You keep referring to 148 coinbase coins, what is the rationale behind this? Why would you prefer using 148 coinbases over legacy coinbases for this purpose?

OK, maybe "post-UASF coinbase coins" is a better term? I just wanted to make it clear that this refers to coins that come from blocks generated after the UASF is activated.

--
Please do not email me anything that you are not comfortable also sharing with the NSA.

On Jun 6, 2017, at 4:59 PM, Kekcoin <kekcoin@protonmail.com> wrote:

You keep referring to 148 coinbase coins, what is the rationale behind this? Why would you prefer using 148 coinbases over legacy coinbases for this purpose?

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

[-- Attachment #2: Type: text/html, Size: 3275 bytes --]

  reply	other threads:[~2017-06-07  0:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 22:39 [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable Tao Effect
2017-06-06 23:02 ` Gregory Maxwell
2017-06-06 23:12   ` Tao Effect
2017-06-07 13:25   ` Nick Johnson
2017-06-07 16:27     ` Tao Effect
2017-06-07 17:35       ` Nick Johnson
2017-06-08  5:44         ` Conner Fromknecht
2017-06-08  6:38           ` Nick Johnson
2017-06-06 23:08 ` Luke Dashjr
2017-06-06 23:19   ` Tao Effect
2017-06-06 23:20 ` Anthony Towns
2017-06-06 23:27   ` Tao Effect
2017-06-06 23:31     ` Tao Effect
2017-06-06 23:59     ` Kekcoin
2017-06-07  0:04       ` Tao Effect
2017-06-07  0:19         ` Kekcoin [this message]
2017-06-07  0:26           ` Tao Effect
2017-06-07  0:29             ` Kekcoin
2017-06-07  0:38               ` Tao Effect
2017-06-07  0:46                 ` Kekcoin
  -- strict thread matches above, loose matches on Subject: below --
2017-06-06 20:43 Tao Effect

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='oSkyoMQ0QQadP3ZDrIU_Xw0sEG8lv5q3B5Kjwnu_MIkvUGmg9TrDn1myLeRhPhyPpGbAgp1QWkerbp76jjptWhh4jz3JXjVycXuXZkxodG8=@protonmail.com' \
    --to=kekcoin@protonmail.com \
    --cc=aj@erisian.com.au \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=contact@taoeffect.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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