From: Prayank <prayank@tutanota•de>
To: jack@squareup•com
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
info@bitcoindefensefund•org
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Thu, 13 Jan 2022 11:13:11 +0100 (CET) [thread overview]
Message-ID: <MtHvJYE--J-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
Hi Jack,
> 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. The Fund will start with a corps of volunteer and part-time lawyers. The board of the Fund will be responsible for determining which lawsuits and defendants it will help defend.
Thanks for helping the developers in legal issues. Appreciate your efforts and I understand your intentions are to help Bitcoin in every possible way.
Positives that I see in this initiative:
1.Developers don't need to worry about rich scammers and can focus on development.
2.Financial help for developers as legal issues can end up in wasting lot of time and money.
3.People who have misused courts to affect bitcoin developers will get better response that they deserve.
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.
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.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 2412 bytes --]
next reply other threads:[~2022-01-13 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 10:13 Prayank [this message]
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
-- 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=MtHvJYE--J-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=info@bitcoindefensefund$(echo .)org \
--cc=jack@squareup$(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