public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeremy <jlrubin@mit•edu>
To: qmccormick13 <qmccormick13@gmail•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 10:34:45 -0800	[thread overview]
Message-ID: <CAD5xwhjoYmTEXmvV6dYMXrOvyzQ9M6CUXZ-Uf8sQDKyRQC0Kpg@mail.gmail.com> (raw)
In-Reply-To: <CAABBXbuxcw+SQz573bRxPdiVq3XYFged=TSmb32ABUfq8_4MoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3765 bytes --]

If I understand the intent of your message correctly, that's unfortunately
not how the law works.

If there is a case that is precedent setting, whether it directly involves
bitcoin or not, a bitcoin focused legal fund might want to either offer
representation or file an amicus brief to guide the court to making a
decision beneficial to Bitcoin Developers.

More than likely, some of these cases would involve developers of
alternative projects (as they might be "ahead of the curve" on legal
problems) and heading off a strong precedent for other communities would be
protective for Bitcoiners in general. As an example, were the developers
building Rollups on Ethereum to face a legal threat, since we might one day
want similar software for Bitcoin, ensuring a good outcome for them helps
Bitcoin.

That said, all organizations must at some point have a defined scope, and
it seems the BLDF is primarily focused for now on things impacting the
developers of Bitcoin or software for bitcoin specifically. I "trust" the
legal team behind BLDF will form a coherent strategy around what is
relevant to Bitcoin defense, even if the particulars of a case are not
directly about Bitcoin.

cheers,

Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>


On Fri, Jan 14, 2022 at 10:25 AM qmccormick13 via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> 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
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 6543 bytes --]

  reply	other threads:[~2022-01-14 18:35 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
2022-01-14 18:34       ` Jeremy [this message]
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=CAD5xwhjoYmTEXmvV6dYMXrOvyzQ9M6CUXZ-Uf8sQDKyRQC0Kpg@mail.gmail.com \
    --to=jlrubin@mit$(echo .)edu \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=info@bitcoindefensefund$(echo .)org \
    --cc=prayank@tutanota$(echo .)de \
    --cc=qmccormick13@gmail$(echo .)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