summaryrefslogtreecommitdiff
path: root/a4/856c6f6e1357a1da30eb6480400e81d7776d7c
blob: 4de745aa654468c1fc0c372ed2f3dc9a57377382 (plain)
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
117
118
Return-Path: <symphonicbtc@proton.me>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 30BBAC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 21 Aug 2023 22:34:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 70BE4408AE
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 21 Aug 2023 22:34:24 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 70BE4408AE
Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key,
 unprotected) header.d=proton.me header.i=@proton.me header.a=rsa-sha256
 header.s=protonmail header.b=jrDHw7L7
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
 by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Bs72QdZgiKRl
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 21 Aug 2023 22:34:22 +0000 (UTC)
Received: from mail-4327.protonmail.ch (mail-4327.protonmail.ch [185.70.43.27])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 3F13240549
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 21 Aug 2023 22:34:22 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 3F13240549
Date: Mon, 21 Aug 2023 22:34:03 +0000
Authentication-Results: mail-4321.protonmail.ch;
 dkim=pass (2048-bit key) header.d=proton.me header.i=@proton.me
 header.b="jrDHw7L7"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me;
 s=protonmail; t=1692657251; x=1692916451;
 bh=MMBHj3GB9x0hx/F32TxhjTbJUe5swxvsokg5p5g8egg=;
 h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
 Message-ID:BIMI-Selector;
 b=jrDHw7L7sWz9kS5dXvxft3UyCWk8irHtW4hqbxkNWvOMoEBHCc0swkHJUobHL5IPD
 pPyjt0e7XkbDsT7+trYCkFi16D8cm0tUPoC+SDp9ClxhO3Dv6Qb27AFrNF4zlkh8ab
 8DyaguawJlEkWlK8xfIqxgAXGF7bCYB2wG8upehKtRAvjekA5yMimolXZuXMs1SGbv
 Rspd+ygQ+Vq5pkiXDJGT7nTn3Oh8422eNxhs7E6k4ntUP8PTZQlvX+HnxEq1Al9cVY
 i1JsRqzOchBAl66Fg7VMy4Y6Pkfe6i/K7Nx9YazScGRtqNlk+/wqKL8IKGRxMwfI0n
 ap/KZWYXNytvw==
To: John Tromp <john.tromp@gmail.com>
From: symphonicbtc <symphonicbtc@proton.me>
Message-ID: <UMOgM6dqQHqgxIoeyCE1ZzBDbU1c2H6oyUCVs4eTgUwozDphZwFdfO4qvnXUMZwYhfShzcaYqmLGN-XrfzyhYKWD8Q8IOD7EJAtdgbqMLe8=@proton.me>
In-Reply-To: <CAOU__fxqf7VpYptKKPpW30RXQHA+g0bA7xy6YOQNy1Of=xYB3A@mail.gmail.com>
References: <mailman.134025.1692632811.956.bitcoin-dev@lists.linuxfoundation.org>
 <CAOU__fxqf7VpYptKKPpW30RXQHA+g0bA7xy6YOQNy1Of=xYB3A@mail.gmail.com>
Feedback-ID: 77757318:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 21 Aug 2023 22:46:21 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Concern about "Inscriptions"
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: Mon, 21 Aug 2023 22:34:25 -0000

It is important to also note that proof of secret key schemes are highly da=
ta inefficient and likely would have a higher cost for users than simply al=
lowing arbitrary data to continue. In ECDSA, purposely re-using k values al=
lows you to encode data in both k and the entire secret key, as both become=
 computable. Or, one could bruteforce a k value to encode data in a sig, as=
 is done in some compromised hardware key exfiltration attacks. Additionall=
y, one can bruteforce keys in order to encode data in the public key.

It is very difficult and expensive to attempt to limit the storage of arbit=
rary data in a system where the security comes from secret keys being arbit=
rary data.

Symphonic

------- Original Message -------
On Monday, August 21st, 2023 at 4:28 PM, John Tromp via bitcoin-dev <bitcoi=
n-dev@lists.linuxfoundation.org> wrote:


> > If we ban "arbitrary data", however you want to define it, then actors =
will
> > simply respond by encoding their data within sets of public keys. Publi=
c
> > key data is indistinguishable from random data, and, unless we are will=
ing
> > to pad the blockchain with proof of knowledge of secret keys, there wil=
l be
> > no way to tell a priori whether a given public key is really a public k=
ey
> > or whether it is encoding an inscription or some other data.
>=20
>=20
> Note that in the Mimblewimble protocol, range proofs already prove
> knowledge of blinding factor in Pedersen commitments, and thus no
> additional padding is needed there to prevent the encoding of spam
> into cryptographic material. This makes pure MW blockchains the most
> inscription/spam resistant [1].
>=20
> [1] https://bitcointalk.org/index.php?topic=3D5437464.msg61980991#msg6198=
0991
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev