From: jack <jack@squareup.com>
To: Prayank <prayank@tutanota.de>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>,
info@bitcoindefensefund.org
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Thu, 13 Jan 2022 18:20:40 +0000 [thread overview]
Message-ID: <F3DA4333-E4BB-4A3F-B050-AA142465F2C8@squareup.com> (raw)
In-Reply-To: <MtHvJYE--J-2@tutanota.de>
Hi Prayank,
> On 13 Jan 2022, at 10:13, Prayank <prayank@tutanota.de> wrote:
> I had few suggestions and feel free to ignore them if they do not make sense:
>
> 1.Name of this fund could be anything and 'The Bitcoin Legal Defense Fund' can be confusing or misleading for newbies. There is nothing official in Bitcoin however people believe things written in news articles and some of them might consider it as an official bitcoin legal fund.
Excellent point. Will come up with a better name.
> 2.It would be better if people involved in such important funds do not comment/influence soft fork related discussions. Example: Alex Morcos had some opinions about activation mechanism during Taproot soft fork IIRC.
Yes. Will think through this and board operating principles we can share publicly, which would probably include criteria for how cases are chosen, to protect against this board and fund influencing direction.
Open to ideas and suggestions on all.
jack
next prev parent reply other threads:[~2022-01-13 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:13 [bitcoin-dev] Bitcoin Legal Defense Fund Prayank
2022-01-13 18:20 ` jack [this message]
2022-01-14 13:21 ` Aymeric Vitte
2022-01-14 18:18 ` qmccormick13
2022-01-14 18:34 ` Jeremy
2022-01-21 14:36 ` Zac Greenwood
2022-01-13 18:28 ` Steve Lee
2022-01-13 18:54 ` Alex Schoof
2022-01-13 19:28 ` Steve Lee
2022-01-13 19:05 ` Jeremy
2022-01-13 20:50 ` Antoine Riard
-- strict thread matches above, loose matches on Subject: below --
2022-01-12 9:59 SatoshiSingh
2022-01-12 0:13 jack
2022-01-12 0:47 ` René Pickhardt
2022-01-12 1:42 ` Christopher Allen
2022-01-13 19:25 ` Alex Morcos
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=F3DA4333-E4BB-4A3F-B050-AA142465F2C8@squareup.com \
--to=jack@squareup.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=info@bitcoindefensefund.org \
--cc=prayank@tutanota.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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