On Sat, Feb 18, 2023 at 02:03:15AM +0200, Peter Todd wrote: > 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? >
By standardness rules (where you can have up to 80-byte pushes), a little over 1%. By consensus (520-byte pushes) less than 0.2%. Perhaps "greatly increase" is a stretch :) but if the fee market is functioning and we're talking about large amounts of data, it's not trivial either. -- Andrew Poelstra Director of Research, Blockstream Email: apoelstra at wpsoftware.net Web: https://www.wpsoftware.net/andrew The sun is always shining in space -Justin Lewis-Webster
signature.asc
Description: PGP signature
_______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
