From: John Tromp <john.tromp@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Concern about "Inscriptions"
Date: Mon, 21 Aug 2023 18:28:50 +0200 [thread overview]
Message-ID: <CAOU__fxqf7VpYptKKPpW30RXQHA+g0bA7xy6YOQNy1Of=xYB3A@mail.gmail.com> (raw)
In-Reply-To: <mailman.134025.1692632811.956.bitcoin-dev@lists.linuxfoundation.org>
> 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. Public
> key data is indistinguishable from random data, and, unless we are willing
> to pad the blockchain with proof of knowledge of secret keys, there will be
> no way to tell a priori whether a given public key is really a public key
> or whether it is encoding an inscription or some other data.
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].
[1] https://bitcointalk.org/index.php?topic=5437464.msg61980991#msg61980991
next parent reply other threads:[~2023-08-21 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.134025.1692632811.956.bitcoin-dev@lists.linuxfoundation.org>
2023-08-21 16:28 ` John Tromp [this message]
2023-08-21 22:34 ` symphonicbtc
2023-08-23 17:34 ` Erik Aronesty
2023-09-06 8:00 vjudeu
-- strict thread matches above, loose matches on Subject: below --
2023-09-03 16:01 vjudeu
2023-09-05 17:49 ` Peter Todd
[not found] <mailman.11.1692705603.26941.bitcoin-dev@lists.linuxfoundation.org>
2023-08-22 14:18 ` GamedevAlice
2023-08-18 20:43 martl.chris
2023-08-21 14:47 ` Russell O'Connor
2023-08-21 14:58 ` rot13maxi
2023-08-22 5:15 ` martl.chris
2023-08-03 13:33 GamedevAlice
2023-08-03 16:03 ` leohaf
2023-08-02 11:07 GamedevAlice
2023-08-02 15:46 ` Luke Dashjr
2023-07-27 19:03 Léo Haf
2023-07-30 18:34 ` rot13maxi
2023-07-27 5:10 vjudeu
2023-07-26 5:30 vjudeu
2023-07-26 9:46 ` leohaf
2023-07-25 14:11 leohaf
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='CAOU__fxqf7VpYptKKPpW30RXQHA+g0bA7xy6YOQNy1Of=xYB3A@mail.gmail.com' \
--to=john.tromp@gmail$(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