From: Michael Naber <mickeybob@gmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Core: The globally aware global consensus network
Date: Mon, 29 Jun 2015 04:33:21 -0400 [thread overview]
Message-ID: <F46592A0-0431-447B-9EBB-4BD71041037D@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Bitcoin is globally aware global consensus.
It means every node both knows about and agrees on every transaction.
Do we need global awareness of every transaction to run a worldwide payment network? Of course not! In fact the limits of today's technology probably would not even allow it.
Global awareness is a finite resource. That's okay; hub and spoke, or other clever designs are going to ensure we can run worldwide transactions without requiring global awareness. That's great!
But even if we have hub and spoke, we still need a "hub" at the center. Bitcoin Core needs to focus on being that hub. It needs to be the best globally aware global consensus network that we can build. Let's put aside our differences and focus on this goal.
Part of building the best network means ensuring that network can operate at the highest capacity technology can allow.
If we run the test-net to show that hardware exists today to safely increase block size to a static 8 MB, then we will have broad developer support to make this happen.
Let's get that done. We can continue to adjust the block size upward in the future as technology permits.
Thoughts?
[-- Attachment #2: Type: text/html, Size: 3936 bytes --]
next reply other threads:[~2015-06-29 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 8:33 Michael Naber [this message]
2015-06-29 9:17 ` [bitcoin-dev] Bitcoin Core: The globally aware global consensus network Pindar Wong
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=F46592A0-0431-447B-9EBB-4BD71041037D@gmail.com \
--to=mickeybob@gmail.com \
--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