From: Murch <murch@murch•one>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Pull-req to remove the arbitrary limits on OP_Return outputs
Date: Wed, 9 Aug 2023 15:06:49 +0200 [thread overview]
Message-ID: <03551f0f-272e-2607-e95a-8ec671cbb9f3@murch.one> (raw)
In-Reply-To: <00feb0f1-ec5a-4fc2-8bff-5acf8616e458@app.fastmail.com>
[-- Attachment #1: Type: text/html, Size: 4857 bytes --]
next prev parent reply other threads:[~2023-08-09 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 20:35 John Light
2023-08-08 1:34 ` ZmnSCPxj
2023-08-09 13:06 ` Murch [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 11:42 Peter Todd
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=03551f0f-272e-2607-e95a-8ec671cbb9f3@murch.one \
--to=murch@murch$(echo .)one \
--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