1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
Return-Path: <christopher.gilliard@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
by lists.linuxfoundation.org (Postfix) with ESMTP id AA42EC000B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Apr 2021 10:14:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 99A698333E
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Apr 2021 10:14:34 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.602
X-Spam-Level:
X-Spam-Status: No, score=0.602 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id XnrhyVLmJhMJ
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Apr 2021 10:14:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-oo1-xc2c.google.com (mail-oo1-xc2c.google.com
[IPv6:2607:f8b0:4864:20::c2c])
by smtp1.osuosl.org (Postfix) with ESMTPS id 4CD7D83218
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Apr 2021 10:14:32 +0000 (UTC)
Received: by mail-oo1-xc2c.google.com with SMTP id
g9-20020a4ad3090000b02901ec6daba49aso2294310oos.6
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 21 Apr 2021 03:14:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=G6kfAoP1TmJMHPjesb9jIQ4zpxvS5lMHlryZ7a8Rskk=;
b=LuU4O5AOae/ZxTqmkXCm1A/TGc0KJXBV58my0W5DsbF6ovZCu9wvqPwwzLCsbbp8N6
mEtgonKBM+MwKcL0bMiz+PCoir9as7yvt+TO5cVmJZi6R4ZmTnu32aB/r3qgFPFf+Kvw
OsaxaxwBt2Yl5XZr0FjxIoO/VhQ90t3EOIHXVR+eAJHJcFKsEvkL1n8ov/kKaG6ZgyxN
AR4CyAubXFjGJ4ily1yAH6e/EhJ9ih6GWBG8enH+PFalopoYWMtplNUUTwxw3addwVRF
9OqsSj6L+LVTv/O7uCYW71v8RlDyuIfwFj98lh4ltu0WcpOqmSlnLyD6Oa9g9e4H0Fy6
hO1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=G6kfAoP1TmJMHPjesb9jIQ4zpxvS5lMHlryZ7a8Rskk=;
b=sR6cZHWyePiblXoIp+0wcL/f7SWvo5+GTL+XeGru9tBjq4ZHVYUg+7xXORZw/iJMsD
jwWpN+gj2a1cWkfIrZWqe1LcYijmTseZAESDTbYZo2I+OWZ06SUyevUWU73/N6oAQFLI
JBYCllAFt1lpYaRlWVnXmr2FeFhpKC9ckQ/apTdRQUqjv9ntlhwg0uX0j/O5SAWZE5mj
0V2DTkdS9DkJ5f14gEvzVuh1Y1mZh3GhNooWv4NIuUB0vO6iLfSSrLd0YoKJhW+Wcy0t
+Er7Cy8qLO0GWb9GbJgcIsomPKHJv9Yz9YErkemBNVrtpIKlATeIsf95ZXcGzw3OOPh1
lIqQ==
X-Gm-Message-State: AOAM532MNBFXnMtMpWbXux2WLxGXP7dh8y8suZWlOvZlsp7kEiVgV2Nq
RjYC9UJW4ur3lEdhDC0ADH7sppqZswMU4gNe5H4=
X-Google-Smtp-Source: ABdhPJxDI4FEfuwL7b6bATpPBDy1U4a1HDLoZMXwJRuAPb7ycsgcCWPL7HRQBAsZCTGNCBHXksBOOZ5ORmWABYlrOns=
X-Received: by 2002:a4a:94c3:: with SMTP id l3mr15565572ooi.12.1619000071287;
Wed, 21 Apr 2021 03:14:31 -0700 (PDT)
MIME-Version: 1.0
References: <MYmfT1n--3-2@tutanota.de>
In-Reply-To: <MYmfT1n--3-2@tutanota.de>
From: Christopher Gilliard <christopher.gilliard@gmail.com>
Date: Wed, 21 Apr 2021 03:14:20 -0700
Message-ID: <CAK=nyAwPryUxknAsxhEXCXzn_CRr0AMTUOKNcO17wnr1huXJWA@mail.gmail.com>
To: Prayank <prayank@tutanota.de>
Content-Type: multipart/alternative; boundary="00000000000023f8e905c078d405"
X-Mailman-Approved-At: Wed, 21 Apr 2021 10:56:11 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPs - notarization protocol and decentralized
storage
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 10:14:34 -0000
--00000000000023f8e905c078d405
Content-Type: text/plain; charset="UTF-8"
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
>
--00000000000023f8e905c078d405
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks Prayank. I think the next step for both of these pr=
oposals 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. May=
be when the APIs are defined they could go into the BIP, but it's proba=
bly better to have in a different document. I also agree with you on Tor.<d=
iv><br></div><div>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. T=
here are a number of "Application" BIPs, which is why I decided i=
t made sense. However, if it's decided there's a better format for =
these BIPs I'm open to it.</div><div><br></div><div>Regards,</div><div>=
Chris</div><div><br></div><div><br></div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Apr 20, 2021 at 9:26 PM Pr=
ayank <<a href=3D"mailto:prayank@tutanota.de">prayank@tutanota.de</a>>=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=20
=20
=20
<div>
<div>Hello Christopher,<br></div><div><br></div><div>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 c=
an just be a LN project instead of BIP? Not the best person to comment on w=
hat can be a BIP.<br></div><div><br></div><div>Few links that you may find =
interesting:<br></div><div><br></div><div><a href=3D"https://github.com/bki=
ac/tarnhelm" target=3D"_blank">https://github.com/bkiac/tarnhelm</a><br></d=
iv><div><br></div><div><a href=3D"https://github.com/ElementsProject/fileba=
zaar" target=3D"_blank">https://github.com/ElementsProject/filebazaar</a><b=
r></div><div><br></div><div>The kind of decentralized storage that I think =
can be helpful for Bitcoin projects:<br></div><div><br></div><div>1.Uses to=
rrents for files and communication required (with Tor)<br></div><div><br></=
div><div>2.Easy to use API to save, read, edit etc. something in a Bitcoin =
project using torrents. Only involve lightning network and payments when sp=
amming can be an issue. For example: If a developer wants users to pay for =
every P2P offer they create using a DEX protocol.<br></div><div><br></div><=
div>Projects that are exploring such options:=C2=A0<a href=3D"https://githu=
b.com/JoinMarket-Org/joinmarket-clientserver/issues/415" target=3D"_blank">=
https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/415</a><br=
></div><div><br></div><div>-- <br></div><div>Prayank</div> </div>
</blockquote></div>
--00000000000023f8e905c078d405--
|
