From: Peter Todd <pete@petertodd•org>
To: Andrew Poelstra <apoelstra@wpsoftware•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Andrew Poelstra via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org>,
vjudeu@gazeta•pl
Subject: Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
Date: Sat, 18 Feb 2023 02:03:15 +0200 [thread overview]
Message-ID: <B837E586-894E-40E8-9814-385EF59402B6@petertodd.org> (raw)
In-Reply-To: <Y/APRs3IPYapIpGg@camus>
On February 18, 2023 1:35:34 AM GMT+02:00, Andrew Poelstra via bitcoin-dev
>You could try statically analyze `<anything>` to determine whether the
>IF branch could ever be taken. For example there is no path through
>the "inscription script" that would result in all the crap being dropped
>by the end of the script, violating the CLEANSTACK rule.
>
>This sort of filtering, assuming it could be reliably and efficiently
>done, would at least force inscription scripts to be "plausible", and
>would greatly increase their space cost by e.g. requiring OP_DROP to be
>added somewhere hundreds of times.
"greatly increase their space cost"?
Tell me, what is the actual % increase to adding OP_DROPs like you propose?
next prev parent reply other threads:[~2023-02-18 0:03 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
2023-02-18 0:03 ` Peter Todd [this message]
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=B837E586-894E-40E8-9814-385EF59402B6@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=apoelstra@wpsoftware$(echo .)net \
--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