From: Alex Morcos <morcos@chaincode•com>
To: "René Pickhardt" <r.pickhardt@googlemail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Thu, 13 Jan 2022 14:25:48 -0500 [thread overview]
Message-ID: <CANvRQdVbKdFETiehfLOiaj=BkmHLvxxZm1-5+fzfXYoKxk15vw@mail.gmail.com> (raw)
In-Reply-To: <CAJ5H3Z7LhFzM4rY=h0H_0t+tFO80SuQ321-a8B-tE3HeWUN1Gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
To belatedly answer Rene's question:
Yes, we hope so. To start, the Fund will focus on the defense of the
pending litigation and new litigation that may arise. However, we intend to
build up the capacity to provide competent third-party advice to developers
on strategies to reduce their liability.
On Tue, Jan 11, 2022 at 7:47 PM René Pickhardt <r.pickhardt@googlemail•com>
wrote:
>
>
> jack via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> schrieb am
> Mi., 12. Jan. 2022, 01:35:
>
>> To Bitcoin Developers:
>>
>> Open-source developers, who are often independent, are especially
>> susceptible to legal pressure.
>
>
> Will the fund eventually also help to educate developers about the risks
> they are facing and which measures can be taken to reduce such risks so
> that legal pressure might not even arise in the first place?
>
> The main purpose of this Fund is to defend developers from lawsuits
>> regarding their activities in the Bitcoin ecosystem, including finding and
>> retaining defense counsel, developing litigation strategy, and paying legal
>> bills. This is a free and voluntary option for developers to take advantage
>> of if they so wish.
>
>
> Thank you!
>
[-- Attachment #2: Type: text/html, Size: 2107 bytes --]
next prev parent reply other threads:[~2022-01-13 19:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-01-12 9:59 SatoshiSingh
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
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
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='CANvRQdVbKdFETiehfLOiaj=BkmHLvxxZm1-5+fzfXYoKxk15vw@mail.gmail.com' \
--to=morcos@chaincode$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=r.pickhardt@googlemail$(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