From: Christopher Gilliard <christopher.gilliard@gmail•com>
To: Prayank <prayank@tutanota•de>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPs - notarization protocol and decentralized storage
Date: Wed, 21 Apr 2021 03:14:20 -0700 [thread overview]
Message-ID: <CAK=nyAwPryUxknAsxhEXCXzn_CRr0AMTUOKNcO17wnr1huXJWA@mail.gmail.com> (raw)
In-Reply-To: <MYmfT1n--3-2@tutanota.de>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Thanks Prayank. I think the next step for both of these proposals is to
define an API. I thought about including that in the BIPs and decided it
wasn't necessary yet to get the ideas across initially. Maybe when the APIs
are defined they could go into the BIP, but it's probably better to have in
a different document. I also agree with you on Tor.
As far as whether this should be a BIP or not, I wondered that same
question. I think the BIP format is well defined and understood so I used
it for this and the other BIPs that I'm currently working on like the
incentivized moderation protocol which is mentioned in this BIP. There are
a number of "Application" BIPs, which is why I decided it made sense.
However, if it's decided there's a better format for these BIPs I'm open to
it.
Regards,
Chris
On Tue, Apr 20, 2021 at 9:26 PM Prayank <prayank@tutanota•de> wrote:
> Hello Christopher,
>
> Decentralized storage as an idea looks interesting. I am researching about
> similar things for one of my Bitcoin project. Although an implementation or
> proof of concept code in the BIP would have been better. Also since this
> involves LN, maybe it can just be a LN project instead of BIP? Not the best
> person to comment on what can be a BIP.
>
> Few links that you may find interesting:
>
> https://github.com/bkiac/tarnhelm
>
> https://github.com/ElementsProject/filebazaar
>
> The kind of decentralized storage that I think can be helpful for Bitcoin
> projects:
>
> 1.Uses torrents for files and communication required (with Tor)
>
> 2.Easy to use API to save, read, edit etc. something in a Bitcoin project
> using torrents. Only involve lightning network and payments when spamming
> can be an issue. For example: If a developer wants users to pay for every
> P2P offer they create using a DEX protocol.
>
> Projects that are exploring such options:
> https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/415
>
> --
> Prayank
>
[-- Attachment #2: Type: text/html, Size: 2854 bytes --]
next prev parent reply other threads:[~2021-04-21 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 4:26 Prayank
2021-04-21 10:14 ` Christopher Gilliard [this message]
2021-04-25 18:29 ` Luke Dashjr
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='CAK=nyAwPryUxknAsxhEXCXzn_CRr0AMTUOKNcO17wnr1huXJWA@mail.gmail.com' \
--to=christopher.gilliard@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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