From: qmccormick13 <qmccormick13@gmail•com>
To: Aymeric Vitte <aymeric@peersm•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Prayank <prayank@tutanota•de>, info@bitcoindefensefund•org
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Fri, 14 Jan 2022 19:18:40 +0100 [thread overview]
Message-ID: <CAABBXbuxcw+SQz573bRxPdiVq3XYFged=TSmb32ABUfq8_4MoQ@mail.gmail.com> (raw)
In-Reply-To: <d1489dc9-e919-fc29-13ac-fcde96f34c50@peersm.com>
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
I very much hope the fund will not finance lawsuits irrelevant to bitcoin.
On Fri, Jan 14, 2022 at 5:23 PM Aymeric Vitte via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> (P2P?) Electronic Cash (Defense?) Fund or Electronic Cash Foundation ?
> More neutral, potentially covering others than Bitcoin, mimicking a bit
> EFF (even if as stated US is not the only target), referring to
> Satoshi's paper where everything started
>
> Maybe I am not up to date but it would be good to know what are the
> current procedures with the Tulip thing
>
> Aymeric
>
>
> Le 13/01/2022 à 19:20, jack via bitcoin-dev a écrit :
> > 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
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists•linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2950 bytes --]
next prev parent reply other threads:[~2022-01-14 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:13 Prayank
2022-01-13 18:20 ` jack
2022-01-14 13:21 ` Aymeric Vitte
2022-01-14 18:18 ` qmccormick13 [this message]
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='CAABBXbuxcw+SQz573bRxPdiVq3XYFged=TSmb32ABUfq8_4MoQ@mail.gmail.com' \
--to=qmccormick13@gmail$(echo .)com \
--cc=aymeric@peersm$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=info@bitcoindefensefund$(echo .)org \
--cc=prayank@tutanota$(echo .)de \
/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