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
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
Return-Path: <raymo@riseup.net>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 55226C000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Jun 2021 20:22:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id 3D357607E5
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Jun 2021 20:22:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5
tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7,
RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=riseup.net
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id c3RRosUZaxwi
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Jun 2021 20:22:09 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
by smtp3.osuosl.org (Postfix) with ESMTPS id 78198606D3
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 18 Jun 2021 20:22:09 +0000 (UTC)
Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.riseup.net",
Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified))
by mx1.riseup.net (Postfix) with ESMTPS id 4G69M51HS8zDq70;
Fri, 18 Jun 2021 13:22:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
t=1624047729; bh=SlINm7l8kDivEP3uLF8WyoKbqNWOB1JjrZvAR+s2V2g=;
h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
b=kFsL0fGF9KEjwT/IT6bQ4gTON3J3NY95TeEYZ0uXJ7+yqierGy6isZ+twCzF/Yqi/
kyo1L6Z5hl81zVwqJ1lYBaPeobWqJL/RmaR3x/uFhdXIvE5Tk5wSwXXHvxutN/wUNc
tgpjkZvO4H7Dh80SpnuL1hB+g44p9FLm/HUXMA3g=
X-Riseup-User-ID: BEC695034D185FCB56D1307D7EBA7291C86924DEB81E3B1BCA3EB4C30B58B3C5
Received: from [127.0.0.1] (localhost [127.0.0.1])
by fews1.riseup.net (Postfix) with ESMTPSA id 4G69M474fgz5w63;
Fri, 18 Jun 2021 13:22:08 -0700 (PDT)
MIME-Version: 1.0
Date: Fri, 18 Jun 2021 13:22:08 -0700
From: raymo@riseup.net
To: Erik Aronesty <erik@q32.com>
In-Reply-To: <CAJowKg+aeWARPDtOrFdwRi2qUuUhSwX-=U3=PY8OUSLgVZzLQA@mail.gmail.com>
References: <bea8122aea550f1141170829aac252af@riseup.net>
<CAJowKg+aeWARPDtOrFdwRi2qUuUhSwX-=U3=PY8OUSLgVZzLQA@mail.gmail.com>
Message-ID: <fa12f4c65dc9806eb9bca7d4a12165a2@riseup.net>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 19 Jun 2021 00:25:39 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Boost Bitcoin circulation,
Million Transactions Per Second with stronger privacy
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 20:22:10 -0000
I think I respond to sybil attack implicitly in Max response. Since the
only consensus must be between issuer and creditor and they already are
in a kind of web of trust connection.
By the way it would be great if you explain the attack scenario in more
detail and our conventional terms such as issuer, creditor, MT, GT, CT,
etc...
definitely we can solve it as well.
On 2021-06-18 13:37, Erik Aronesty wrote:
> It is vulnerable to sybil attacks or where the recipient is a victim
> of a proxy attack. If the recipient is not connected to a valid
> Network, then double spends could be allowed.
>
> as long as this protocol is intended for use of transactions around a
> dollar or so I don't see that being a financially lucrative attack.
>
> However consider a large department store. If I put a "fence" around
> that store and control all of its outbound peer connections, I can
> then allow double spends for the duration of my visit at the store.
>
> In order to defend against this large retailers would have to use
> distributed / trusted nodes and certificates.
>
> On Thu, Jun 17, 2021, 4:14 PM raymo via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> Hi,
>> I have a proposal for improve Bitcoin TPS and privacy, here is the
>> post.
>>
> https://raymo-49157.medium.com/time-to-boost-bitcoin-circulation-million-transactions-per-second-and-privacy-1eef8568d180
>> https://bitcointalk.org/index.php?topic=5344020.0
>> Can you please read it and share your idea about it.
>>
>> Cheers
>> Raymo
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
