1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1YshAR-0006zV-Fp
for bitcoin-development@lists.sourceforge.net;
Thu, 14 May 2015 00:38:27 +0000
Received: from mail-ob0-f182.google.com ([209.85.214.182])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YshAQ-0003Ej-Ny
for bitcoin-development@lists.sourceforge.net;
Thu, 14 May 2015 00:38:27 +0000
Received: by obfe9 with SMTP id e9so42512564obf.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 May 2015 17:38:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=LMtghqKc8v+CT2ZuWCFl93Ia427RdskJKN5Xd8xkOAg=;
b=Og7ikCLgfhJBZa3pYCNhm+/5s0O5z5hkQPKJH1UnFnWKSk73sShDf8PGKr2ZFa6JxP
EyZIKfZIXK65g7vY+DmxjkOhLlKhZitXkDJGU6S8MDnEXv4YbE4zcsffxqlSQSnH7DjZ
NdPnLB+H3aYkh0rtLSs0zrylr+ZgX8tnc9P0ZNL1q1LTcYXa2sCS+9WXOqLufigg+HHY
YX/WVUwZCOqeCQ9YZ4wFl1OphgEMtEkSIpVlUcEZxjgAt5PCZFgDpOaIAjnCZhAVjHwo
tyK15KdsfMTAit+U1tVgYWznMR6yE6PqRzPsOeiaaf09/vv4/9D33hr7od4FgDqhthEA
UBgg==
X-Gm-Message-State: ALoCoQmPXlWMGjkcQwCYSIIXtJUmQ/r0Ef/llHYv1S27dRaMGKDJe9q7qORM4EVC5X+7uy23zKyf
MIME-Version: 1.0
X-Received: by 10.182.119.132 with SMTP id ku4mr1166951obb.34.1431560765057;
Wed, 13 May 2015 16:46:05 -0700 (PDT)
Received: by 10.202.83.88 with HTTP; Wed, 13 May 2015 16:46:04 -0700 (PDT)
In-Reply-To: <CAE28kURWFveC0B-WvFebMpGm1GY-8juxQ+UDpuYtOwVnbOgu-A@mail.gmail.com>
References: <5550D8BE.6070207@electrum.org>
<ce3d34c92efd1cf57326e4679550944e@national.shitposting.agency>
<CABsx9T1VgxEJWxrYTs+2hXGnGrSLGJ6mVcAexjXLvK7Vu+e3EA@mail.gmail.com>
<5551F376.4050008@electrum.org>
<CABsx9T1h7p3hDr7ty43uxsYs-oNRpndzg=dowST2tXtogxRm2g@mail.gmail.com>
<555210AF.3090705@electrum.org>
<CABsx9T3AxM3et7hgXx3+Rn3BvhQkF-Cn797sHcyztkMpD1UQmA@mail.gmail.com>
<55531E19.3090503@electrum.org>
<CAE-z3OXa8vk6Q1EBChoRYDOLKw--CXNXz4AokXCbVam_8LFFDg@mail.gmail.com>
<CAE28kURWFveC0B-WvFebMpGm1GY-8juxQ+UDpuYtOwVnbOgu-A@mail.gmail.com>
Date: Thu, 14 May 2015 01:46:04 +0200
Message-ID: <CABm2gDoOGcdUeo_xgPp7w7AFs3Fza5VdeqSyV-T9MNhuN3RMeA@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1YshAQ-0003Ej-Ny
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Long-term mining incentives
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 00:38:27 -0000
On Wed, May 13, 2015 at 12:31 PM, Alex Mizrahi <alex.mizrahi@gmail.com> wrote:
> But this matters if a new node has access to the globally strongest chain.
> If attacker is able to block connections to legitimate nodes, a new node
> will happily accept attacker's chain.
If you get isolated from the network you may not get the longest valid
chain. I don't think any other consensus mechanism deals with this
better than Bitcoin.
> So PoW, by itself, doesn't give strong security guarantees. This problem is
> so fundamental people avoid talking about it.
>
> In practice, Bitcoin already embraces "weak subjectivity" e.g. in form of
> checkpoints embedded into the source code. So it's hard to take PoW purists
> seriously.
Checkpoints are NOT part of the consensus rules, they're just an
optimization that can be removed.
Try keeping the genesis block as your only checkpoint and rebuild: it
will work. You can also define your own checkpoints, there's no need
for everyone to use the same ones.
In a future with committed utxo the optimization could be bigger, but
still, we shouldn't rely on checkpoints for consensus, they're just an
optimization and you should only trust checkpoints that are buried in
the chain. Trusting a committed utxo checkpoint from 2 years ago
doesn't seem very risky. If the code is not already done (not really
sure if it was done as part of auto-prune), we should be prepared for
reorgs that invalidate checkpoints.
So, no, Bitcoin does NOT rely on that "weak subjectivity" thing.
|
