From: Greg Tonoski <gregtonoski@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>,
Victor Kolobov <victor.k@starkware•co>
Subject: Re: [bitcoindev] OP_CAT Research Fund sponsored by StarkWare
Date: Thu, 29 Aug 2024 15:43:14 +0200 [thread overview]
Message-ID: <CAMHHROw0KfQ=U-m-FaJ_nr4mMKu8eQ8bz3gYAmqAgiV2VGcYEA@mail.gmail.com> (raw)
In-Reply-To: <04b61777-7f9a-4714-b3f2-422f99e54f87n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2347 bytes --]
@Admin
I am reporting this thread as spam. "Posts must concern development of
bitcoin protocol and be technical or academic (patches, PRs, BIPs, academic
papers)."
On Thu, 29 Aug 2024, 15:27 'Victor Kolobov' via Bitcoin Development Mailing
List, <bitcoindev@googlegroups.com> wrote:
> Hey all,
>
>
> StarkWare has announced a $1 million bounty for compelling arguments
> either in favor of or against the activation of OP_CAT. This bounty is
> overseen by a committee which includes the following members:
>
> -
>
> Andrew Poelstra (Chair) - Blockstream
> -
>
> Victor Kolobov (Secretary General) - StarkWare
> -
>
> Avihu Levy - StarkWare
> -
>
> Clara Shinkleman - Chaincode
> -
>
> Ethan Heilman - BastionZero
> -
>
> Louis Guthman - StarkWare
> -
>
> Olaoluwa Osuntokun - Lightning Labs
> -
>
> Robin Linus - ZeroSync
> -
>
> Tadge Dryja
>
> The bounty is intended to gather well-reasoned arguments from the
> community, either supporting or opposing the activation of OP_CAT. Topics
> of interest include but are not limited to: the security implications of
> OP_CAT activation on Bitcoin, OP_CAT-based computing and locking script
> logic on Bitcoin, applications and protocols utilizing OP_CAT on Bitcoin,
> and general research related to OP_CAT and its impact.
>
> Please apply here <https://starkware.co/submission-proposals/>!
>
> --
> 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/04b61777-7f9a-4714-b3f2-422f99e54f87n%40googlegroups.com
> <https://groups.google.com/d/msgid/bitcoindev/04b61777-7f9a-4714-b3f2-422f99e54f87n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CAMHHROw0KfQ%3DU-m-FaJ_nr4mMKu8eQ8bz3gYAmqAgiV2VGcYEA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 12102 bytes --]
next prev parent reply other threads:[~2024-08-29 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 13:18 'Victor Kolobov' via Bitcoin Development Mailing List
2024-08-29 13:43 ` Greg Tonoski [this message]
2024-08-29 14:08 ` Matt Corallo
2024-08-29 16:08 ` [bitcoindev] " /dev /fd0
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='CAMHHROw0KfQ=U-m-FaJ_nr4mMKu8eQ8bz3gYAmqAgiV2VGcYEA@mail.gmail.com' \
--to=gregtonoski@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
--cc=victor.k@starkware$(echo .)co \
/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