Delivery-date: Fri, 03 Oct 2025 09:33:26 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as permitted sender) client-ip=172.104.61.193;
Date: Sat, 4 Oct 2025 02:15:37 +1000
From: Anthony Towns <aj@erisian.com.au>
To: Andrew Poelstra <apoelstra@wpsoftware.net>,
	Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: [BIP Proposal] Limit ScriptPubkey Size >= 520
 Bytes Consensus.
Message-ID: <aN_2qZzAu9gxa1h0@erisian.com.au>
References: <6f6b570f-7f9d-40c0-a771-378eb2c0c701n@googlegroups.com>
 <842930fb-bede-408a-8380-776d4be4e094n@googlegroups.com>
 <aN_Wz5YbZ9NieQu0@mail.wpsoftware.net>
 <CALiT-ZpJ_F2UrvUwRjgMukxQJ+s8GVzgDCHWt=zMR+HkMDDWWQ@mail.gmail.com>
 <aN_k1EAXZ0schWDs@mail.wpsoftware.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline
In-Reply-To: <aN_k1EAXZ0schWDs@mail.wpsoftware.net>
X-Spam_score: -0.0
X-Spam_bar: /
X-Original-Sender: aj@erisian.com.au
X-Original-Authentication-Results: gmr-mx.google.com;       spf=pass
 (google.com: domain of aj@erisian.com.au designates 172.104.61.193 as
 permitted sender) smtp.mailfrom=aj@erisian.com.au
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.8 (/)

On Fri, Oct 03, 2025 at 02:59:32PM +0000, Andrew Poelstra wrote:
> If "it's cheaper to use witness data" were enough of a barrier, nobody
> would be using OP_RETURN outputs today except for opentimestamps and
> maybe some other super-low-load applications.

It isn't chepaer to use witness data until you're publishing more than
~143 bytes of data, due to the overhead of the setup transaction. (It's
also not cheaper if you want extremely easy proof of publication of
the data)

Excluding the couple of months between the topic of increasing the
OP_RETURN limit was raised on this list and the increased limit was
merged into Bitcoin Core master, there have, in fact, been very few
OP_RETURN outputs generated that are above the ~143B size. In particular,
between blocks 900k and 915,843 I get:

  15,003,149 total OP_RETURN outputs
         131 OP_RETURN outputs larger than 83 bytes
          81 OP_RETURN outputs of 144 bytes or more
      19,707 OP_RETURN outputs with non-zero value

cf https://github.com/bitcoin/bitcoin/pull/33453#issuecomment-3341177765

Cheers,
aj

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/aN_2qZzAu9gxa1h0%40erisian.com.au.