From: Tao Effect <contact@taoeffect•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable
Date: Tue, 6 Jun 2017 13:43:25 -0700 [thread overview]
Message-ID: <BDD17E4F-254F-426B-827A-E43CC07EFC27@taoeffect.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2050 bytes --]
This is just me putting in my formal objection to BIP148 and BIP149 based on my experience with the ETH/ETC hard fork and involvement in that drama.
First, it's important to note that ETC/ETH HF is a very different situation from BIP148 and all other soft-forks. To those on this mailing list, the reasons should be self-evident (one results in two incompatible chains, the other doesn't).
However, replay attacks are common to both possibilities (i.e. when BIP148 has <51% hash power).
I believe the severity of replay attacks is going unvoiced and is not understood within the bitcoin community because of their lack of experience with them.
I further believe that replay attacks are the #1 issue with BIP148, BIP149, etc., superseding wipeout attacks in severity.
These are not baseless beliefs, they're born out of experience and I think anyone will reach the same conclusion upon study.
In a nutshell, replay attacks mean that all talk of there being potentially "two coins" as a result of BIP148 is basically nonsense.
Replay attacks effectively eliminate that possibility.
When users go to "sell their legacy coins", they've just sold their 148 coins, and vice versa.
Both of the coin-splitting techniques given so far by the proponents BIP148 are also untenable:
- Double-spending to self with nLockTime txns is insanely complicated, risky, not guaranteed to work, extremely time consuming, and would likely result in a massive increase in backlogged transactions and increased fees.
- Mixing with 148 coinbase txns destroys fungibility.
Without a coin, there is no real threat from BIP148. Without that threat, there is no point to BIP148, and the miners know this.
These and other concerns are outlined and explained in more detail in this conversation I had yesterday with John Light:
https://www.youtube.com/watch?v=33rL3-p8cPw <https://www.youtube.com/watch?v=33rL3-p8cPw>
Cheers,
Greg Slepak
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
[-- Attachment #1.2: Type: text/html, Size: 5266 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2017-06-07 8:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 20:43 Tao Effect [this message]
2017-06-06 22:39 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
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
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=BDD17E4F-254F-426B-827A-E43CC07EFC27@taoeffect.com \
--to=contact@taoeffect$(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