From: Nick Johnson <nick@ethereum•org>
To: Tao Effect <contact@taoeffect•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Replay attacks make BIP148 and BIP149 untennable
Date: Wed, 07 Jun 2017 17:35:17 +0000 [thread overview]
Message-ID: <CAFz7pMvk5acuXRXPiMwo63A=RgdnhFXrMWmED3JLXXP5BPMf6g@mail.gmail.com> (raw)
In-Reply-To: <F9930B98-BBCC-4B4D-B938-AE2CFB7721AD@taoeffect.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On Wed, Jun 7, 2017 at 5:27 PM Tao Effect <contact@taoeffect•com> wrote:
> Nick,
>
> Please don't spread misinformation. Whatever you think of the DAO hard
> fork, it's a simple fact that the Ethereum ledger was not edited.
>
>
> This sort of email is unhelpful to this conversation, and it certainly
> doesn't help with the perception that Ethereum is nothing but a bunch of
> hypocritical Bankers 2.0.
>
>
> Everyone knows you didn't edit Ethereum Classic, but the the hard fork,
> which was re-branded as Ethereum, was edited.
>
That's not what I was suggesting. My point is that the ledger was never
edited. An 'irregular state change' was added at a specific block height,
but the ledger remains inviolate.
I'm sure I don't have to explain the difference between the ledger and the
state to you, or why it's significant that the ledger wasn't (and can't be,
practically) modified.
-Nick
> - Greg
>
> --
> Please do not email me anything that you are not comfortable also sharing with
> the NSA.
>
> On Jun 7, 2017, at 6:25 AM, Nick Johnson <nick@ethereum•org> wrote:
>
> On Wed, Jun 7, 2017 at 12:02 AM Gregory Maxwell via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> On Tue, Jun 6, 2017 at 10:39 PM, Tao Effect via bitcoin-dev
>> <bitcoin-dev@lists•linuxfoundation.org> wrote:
>> > 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.
>>
>> Please don't insult our community-- the issues with replay were
>> pointed out by us to Ethereum in advance and were cited specifically
>> in prior hardfork discussions long before Ethereum started editing
>> their ledger for the economic benefit of its centralized
>> administrators.
>
>
> Please don't spread misinformation. Whatever you think of the DAO hard
> fork, it's a simple fact that the Ethereum ledger was not edited.
>
> -Nick Johnson
>
>
>
[-- Attachment #2: Type: text/html, Size: 5476 bytes --]
next prev parent reply other threads:[~2017-06-07 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- 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='CAFz7pMvk5acuXRXPiMwo63A=RgdnhFXrMWmED3JLXXP5BPMf6g@mail.gmail.com' \
--to=nick@ethereum$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=contact@taoeffect$(echo .)com \
/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