blob: b70f3c400c31c508afcff7c1dc46f132d90a78f6 (
plain)
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <molec@gmx.de>) id 1RcxBg-00028p-1G
for bitcoin-development@lists.sourceforge.net;
Tue, 20 Dec 2011 10:44:48 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmx.de
designates 213.165.64.23 as permitted sender)
client-ip=213.165.64.23; envelope-from=molec@gmx.de;
helo=mailout-de.gmx.net;
Received: from mailout-de.gmx.net ([213.165.64.23])
by sog-mx-4.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1RcxBa-0008UU-BZ for bitcoin-development@lists.sourceforge.net;
Tue, 20 Dec 2011 10:44:47 +0000
Received: (qmail invoked by alias); 20 Dec 2011 10:44:36 -0000
Received: from e176114117.adsl.alicedsl.de (EHLO zero) [85.176.114.117]
by mail.gmx.net (mp019) with SMTP; 20 Dec 2011 11:44:36 +0100
X-Authenticated: #47824777
X-Provags-ID: V01U2FsdGVkX19zg8QTA7lzV9Jh0v0DhFWxvUur4sCCLe/5qGIm2Y
lsMkaq2Baux+pb
Date: Tue, 20 Dec 2011 11:44:35 +0100
From: Nicolas Fischer <molec@gmx.de>
To: bitcoin-development@lists.sourceforge.net
Message-Id: <20111220114435.8a73a039.molec@gmx.de>
In-Reply-To: <CA+s+GJAcLa9o9H7GfEGeer0+HQE7g7_5EA=Fiii94hxeJiTqkw@mail.gmail.com>
References: <CABr1YTebhitO4g-SarZ7H=aoG9a8zW1wd0rfR32o8i0vODbLJw@mail.gmail.com>
<82659F61-0449-47BB-88DC-497E0D02F8A1@ceptacle.com>
<CALxbBHUXEJLRDZ=RS1vuvkm7rDjFUPir0sU__f6TJXiTTQxWzA@mail.gmail.com>
<4EEE58CA.5090902@justmoon.de> <4EEFAFFB.10508@parhelic.com>
<CA+s+GJAcLa9o9H7GfEGeer0+HQE7g7_5EA=Fiii94hxeJiTqkw@mail.gmail.com>
X-Mailer: Sylpheed 2.6.0 (GTK+ 2.24.4; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(molec[at]gmx.de)
-0.0 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1RcxBa-0008UU-BZ
Subject: Re: [Bitcoin-development] Protocol extensions
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 20 Dec 2011 10:44:48 -0000
On Tue, 20 Dec 2011 10:10:23 +0100
Wladimir <laanwj@gmail.com> wrote:
> Probably would need to package the block chain with it, as downloading that
> over Tor takes ages and causes unnecessary load on the network...
I actually started a freenet plugin for blockchain distribution in summer (first rough steps only). Freenet seems really fit for this purpose since its mechanisms to provide wider storage (and thus faster requesting) for much-requested keys should help a lot here. Also freenet storage is decentralized, so that's another plus that goes hand-in-hand with bitcoin principles.
There's already a specification for "btcfn" which was done in 2010: https://bitcointalk.org/index.php?topic=55089.msg655410#msg655410
I stopped work on this because other people were supposedly working on it. I asked da2ce7 about it at the conference and he said progress was "slow".
I totally agree with the sentiment that these features should not be implemented in the bitcoin node itself but outsourced to the established systems, both because it's hard and also for "hiding traffic in the masses".
--
Nicolas Fischer <molec@gmx.de>
|
