public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: SatoshiSingh <SatoshiSingh@protonmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Cc: "info@bitcoindefensefund•org" <info@bitcoindefensefund•org>
Subject: Re: [bitcoin-dev] Bitcoin Legal Defense Fund
Date: Wed, 12 Jan 2022 09:59:07 +0000	[thread overview]
Message-ID: <PgkH7Jx4gVyX0MdONFmDYq5Mp8-zV43pnHMrlrW1ESDNAa03D9B4U0YhJcoH0aWPFs9Gg3jdwKpoJqL2LhE1q7xZkHI3ZOZK7Iv4g0Zadfc=@protonmail.com> (raw)

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

> 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.

Here in India we have the Internet Freedom Foundation that does something similar but for digital freedom and privacy. They've been supportive to bitcoin and it would be cool if we can include them in this.

https://internetfreedom.in/

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

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

             reply	other threads:[~2022-01-12  9:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  9:59 SatoshiSingh [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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='PgkH7Jx4gVyX0MdONFmDYq5Mp8-zV43pnHMrlrW1ESDNAa03D9B4U0YhJcoH0aWPFs9Gg3jdwKpoJqL2LhE1q7xZkHI3ZOZK7Iv4g0Zadfc=@protonmail.com' \
    --to=satoshisingh@protonmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=info@bitcoindefensefund$(echo .)org \
    /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