From: "Russell O'Connor" <roconnor@blockstream•com>
To: vjudeu@gazeta•pl,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
Date: Sat, 18 Feb 2023 13:03:45 -0500 [thread overview]
Message-ID: <CAMZUoKmTNQd9k0h2T2Vv0Nn2M4JEvAo9NC7FL5EdJ+45KL4VSA@mail.gmail.com> (raw)
In-Reply-To: <177848612-ad2b15230d78bcd732bbe8621af89a1e@pmq3v.m5r2.onet>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On Sat, Feb 18, 2023 at 5:11 AM vjudeu via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Also, it gives us a hint, that if any Script upgrade will be considered in
> the future, we can think about doing it in a way, where unused parts can be
> pruned, without invalidating signatures.
>
FWIW, pruning unused case branches is a core design principle of the
Simplicity language I am developing.
That being said, even this is not enough to thwart agents that specifically
desire to post unused data blobs as part of their programs. This is
largely because there are many mathematical expressions for what is
equivalently an identity function. Think computing (x ^ 257) mod 257 (see
Fermat's little theorem).
Even in Simplicity users can write Word *<some data blob>*; unit which is
roughly equivalent PUSH *<data blob>* DROP in Script. I don't even bother
trying to prevent it. Doing so just adds more consensus complexity, and
only raises the bar slightly on how to work around it.
Simplicity's pruning is instead meant as a way to (usually) lower costs for
users who aren't actively trying to spam the network.
[-- Attachment #2: Type: text/html, Size: 1662 bytes --]
next prev parent reply other threads:[~2023-02-18 18:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 12:34 alicexbt
2023-02-17 14:56 ` vjudeu
2023-02-17 23:35 ` Andrew Poelstra
2023-02-17 23:39 ` Andrew Poelstra
2023-02-18 9:48 ` vjudeu
2023-02-18 18:03 ` Russell O'Connor [this message]
2023-02-18 0:03 ` Peter Todd
2023-02-18 1:28 ` Andrew Poelstra
2023-02-22 16:39 ` Peter Todd
2023-02-19 0:33 ` alicexbt
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=CAMZUoKmTNQd9k0h2T2Vv0Nn2M4JEvAo9NC7FL5EdJ+45KL4VSA@mail.gmail.com \
--to=roconnor@blockstream$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=vjudeu@gazeta$(echo .)pl \
/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