public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Prayank <prayank@tutanota.de>
To: christopher.gilliard@gmail.com
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPs - notarization protocol and decentralized storage
Date: Wed, 21 Apr 2021 06:26:26 +0200 (CEST)	[thread overview]
Message-ID: <MYmfT1n--3-2@tutanota.de> (raw)

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

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: 1630 bytes --]

             reply	other threads:[~2021-04-21  4:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21  4:26 Prayank [this message]
2021-04-21 10:14 ` [bitcoin-dev] BIPs - notarization protocol and decentralized storage Christopher Gilliard
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=MYmfT1n--3-2@tutanota.de \
    --to=prayank@tutanota.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=christopher.gilliard@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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