From: Ethan Heilman <eth3rs@gmail•com>
To: bitcoindev@googlegroups.com
Cc: Armin Sabouri <armins88@gmail•com>
Subject: [bitcoindev] Re: Updated BIP for OP_CAT
Date: Mon, 22 Apr 2024 17:51:35 -0400 [thread overview]
Message-ID: <CAEM=y+V7QUHoPPhEfg7uxdK8s66-gHgkqLKAV8WuPiN-pUWABQ@mail.gmail.com> (raw)
In-Reply-To: <CAEM=y+X-a3VoJ1urjBFhxGpaRzN9dgPr-z6u+YottNsMBT03Sg@mail.gmail.com>
A number of people have privately sent me questions about the status
of the BIP number for OP_CAT. I want to publicly clarify two points in
regards to the OP_CAT BIP:
i. The OP_CAT BIP authors, Armin and I, have formally requested a BIP number,
ii. and no BIP number has yet been assigned (despite what is being
said on twitter).
On Tue, Apr 16, 2024 at 3:03 PM Ethan Heilman <eth3rs@gmail•com> wrote:
>
> Hi everyone,
>
> We've recently made a number of updates to the OP_CAT BIP proposal including adding a rationale section, an expanded backwards compatibility section and an updated reference implementation.
>
> It can be found as a PR to the bitcoin/bips repo here:
> https://github.com/bitcoin/bips/pull/1525
> or as BINANA BIN-2024-0001:
> https://github.com/bitcoin-inquisition/binana/blob/master/2024/BIN-2024-0001.md
>
> Thanks,
> Ethan
>
--
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 on the web visit https://groups.google.com/d/msgid/bitcoindev/CAEM%3Dy%2BV7QUHoPPhEfg7uxdK8s66-gHgkqLKAV8WuPiN-pUWABQ%40mail.gmail.com.
prev parent reply other threads:[~2024-04-24 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 19:03 [bitcoindev] " Ethan Heilman
2024-04-22 16:09 ` [bitcoindev] " Ali Sherief
2024-04-26 0:34 ` Ethan Heilman
2024-04-22 21:51 ` Ethan Heilman [this message]
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='CAEM=y+V7QUHoPPhEfg7uxdK8s66-gHgkqLKAV8WuPiN-pUWABQ@mail.gmail.com' \
--to=eth3rs@gmail$(echo .)com \
--cc=armins88@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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