summaryrefslogtreecommitdiff
path: root/00/23ba753a90eac903c0cdefdfced400e0ebb398
blob: aa04a96bda7e460dd76688c2ebdce1b1b55a92a3 (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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
Return-Path: <staf@stafverhaegen.be>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 874DA5AC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun,  2 Apr 2017 19:45:17 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from lvps83-169-4-30.dedicated.hosteurope.de
	(lvps83-169-4-30.dedicated.hosteurope.de [83.169.4.30])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BB0B11B9
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun,  2 Apr 2017 19:45:16 +0000 (UTC)
Received: (qmail 8159 invoked from network); 2 Apr 2017 21:45:15 +0200
Received: from unknown (HELO hpdc7800) (10.0.0.1)
	by 10.0.0.2 with (AES128-SHA encrypted) SMTP; 2 Apr 2017 21:45:15 +0200
Message-ID: <1491162311.7267.9.camel@stafverhaegen.be>
From: Staf Verhaegen <staf@stafverhaegen.be>
To: bitcoin-dev@lists.linuxfoundation.org
Date: Sun, 02 Apr 2017 21:45:11 +0200
In-Reply-To: <CAD1TkXug2qFggztJL=Z7Thzx13E6ga-2Ps9yZFzonn2YjStrcg@mail.gmail.com>
References: <CALJP9GB2Fds8m9JpaVv0NxGDr579BtR9RMs7-KNSLkK8Mz7LoA@mail.gmail.com>
	<CALJP9GAOgpSAhrrYFPRbGKZXwqZn_oDUmv6B7wcvwxcZufDd0g@mail.gmail.com>
	<CALJP9GDkdxsvOZHJxzx+0pvjWBAkAswZCWXcp=zL7LNMRNfCOg@mail.gmail.com>
	<CALJP9GBk4gG0H+tEJmEiz=0+LAQoe6_sL1Fv-BCJSfmvfY8PRA@mail.gmail.com>
	<CALJP9GDH1xQ-cYc1SN6jejXDA49eiy_OR49XLLWd+=VdNo7ekA@mail.gmail.com>
	<CAFVRnyq07qNappzwEmB_e+xCKPyCzHcWbnTDWCdeWjrsMMioLQ@mail.gmail.com>
	<CAD1TkXsfb7VC7stXV33me1PDem750adpyETg-finKyjnV=Syxg@mail.gmail.com>
	<61B9AE0D-5A58-4A72-8834-8ED164ED627F@gmail.com>
	<CAD1TkXug2qFggztJL=Z7Thzx13E6ga-2Ps9yZFzonn2YjStrcg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256";
	protocol="application/pgp-signature"; boundary="=-zC6bwyrUj5sRj6kDvd+5"
X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) 
Mime-Version: 1.0
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_00,HELO_DYNAMIC_IPADDR
	autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Sun, 02 Apr 2017 19:51:31 +0000
Subject: Re: [bitcoin-dev] High fees / centralization
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Sun, 02 Apr 2017 19:45:17 -0000


--=-zC6bwyrUj5sRj6kDvd+5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Jared Lee Richardson via bitcoin-dev schreef op do 30-03-2017 om 19:01
[-0700]:
> That would be blockchain sharding.
>=20
> Would be amazing if someone could figure out how to do it trustlessly.
> So far I'm not convinced it is possible to resolve the conflicts
> between the shards and commit transactions between shards.

I'm thinking more of a system where different nodes can agree to do part
of the transaction processing. In that way 20000 nodes could work like
5000 full nodes.

greets,
Staf.



--=-zC6bwyrUj5sRj6kDvd+5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EABEIAAYFAljhVMoACgkQWIjyN0LdGqyKrAD/fWevj+fOlptIV7mINLaRZvGd
mGNQZeiwjbfPTpxGolsBAICYjEneNxA9pQkHZsyZMg96dNVrSKDbvFzly7BZaHwB
=PbGA
-----END PGP SIGNATURE-----

--=-zC6bwyrUj5sRj6kDvd+5--