From: Staf Verhaegen <staf@stafverhaegen.be>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] High fees / centralization
Date: Sun, 02 Apr 2017 21:45:11 +0200 [thread overview]
Message-ID: <1491162311.7267.9.camel@stafverhaegen.be> (raw)
In-Reply-To: <CAD1TkXug2qFggztJL=Z7Thzx13E6ga-2Ps9yZFzonn2YjStrcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Jared Lee Richardson via bitcoin-dev schreef op do 30-03-2017 om 19:01
[-0700]:
> That would be blockchain sharding.
>
> 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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2017-04-02 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALJP9GB2Fds8m9JpaVv0NxGDr579BtR9RMs7-KNSLkK8Mz7LoA@mail.gmail.com>
[not found] ` <CALJP9GAOgpSAhrrYFPRbGKZXwqZn_oDUmv6B7wcvwxcZufDd0g@mail.gmail.com>
[not found] ` <CALJP9GDkdxsvOZHJxzx+0pvjWBAkAswZCWXcp=zL7LNMRNfCOg@mail.gmail.com>
[not found] ` <CALJP9GBk4gG0H+tEJmEiz=0+LAQoe6_sL1Fv-BCJSfmvfY8PRA@mail.gmail.com>
2017-03-30 15:38 ` [bitcoin-dev] High fees / centralization Tom Harding
2017-03-30 16:14 ` David Vorick
2017-03-30 21:52 ` Jared Lee Richardson
2017-03-31 1:39 ` Vladimir Zaytsev
2017-03-31 2:01 ` Jared Lee Richardson
2017-03-31 2:26 ` Vladimir Zaytsev
2017-04-02 19:45 ` Staf Verhaegen [this message]
2017-03-31 1:13 ` Tom Harding
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=1491162311.7267.9.camel@stafverhaegen.be \
--to=staf@stafverhaegen.be \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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