From: kjj <bitcoin-devel@jerviss.org>
To: Eric Martindale <eric@ericmartindale.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Date: Mon, 07 Apr 2014 22:13:59 -0500 [thread overview]
Message-ID: <53436977.4030808@jerviss.org> (raw)
In-Reply-To: <CAAf19Wrz0u_e5V9Gb=_CAG=mHtE9nA_VETgYZeCXZqwaGeYKuQ@mail.gmail.com>
Multi-sig requires infrastructure. It isn't a magic wand that we can
wave to make everyone secure. The protocols and techniques necessary
don't exist yet, and apparently no one has much of an incentive to
create them.
I mean no offense, and I don't mean to pick on you. Your post stuck out
while I was reading. Secure multi-sig is what we all want, but wanting
apparently isn't enough to make it happen.
Other random notes from reading this 50+ post thread:
Perhaps we should have a config flag to prevent a node from serving IBD
to new nodes. IBD crushes marginal machines, particularly those with
spinning disks. This has been extensively discussed elsewhere.
The ideal IBD hosts are serving the blockchain out of a RAM disk. Is
there any interest in setting up a network of volunteers to host
expensive servers with fast connections? It doesn't look too terribly
difficult to figure out when a node has stopped asking for blocks in
bulk, so we could add another config flag to eject nodes once they are
done booting.
Even ignoring IBD, I think that we are gradually outgrowing cheapass
hosting options. Personally, I long ago gave up on answering forum
questions about running nodes on virtual servers and VPSs. It is
certainly still possible to run bitcoind on small boxes, but it isn't
trivial any more. (Anyone running on less than my Athlon XP 1800+ with
896 MB RAM?) If we want those nodes back, we need to optimize the hell
out of the memory use, and even that might not be enough.
Eric Martindale wrote:
>
> We need to make it so mind-numbingly simple to "run Bitcoin correctly"
> that the average user doesn't find reasons to do so in the course of
> normal use. Right now, Coinbase and Bitstamp are winning in the user
> experience battle, which technically endanger the user, and by proxy
> the Bitcoin network.
>
> Multi-sig as a default is a start. It won't succeed unless the user
> experience is simply better than trusted third parties, but we need to
> start the education process with the very basic fundamental: trusting
> a third-party with full access to your Bitcoin is just replacing one
> centralized banking system with another.
>
>
next prev parent reply other threads:[~2014-04-08 3:14 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:34 [Bitcoin-development] Why are we bleeding nodes? Mike Hearn
2014-04-07 12:17 ` Ricardo Filipe
2014-04-07 13:43 ` Andreas Schildbach
2014-04-07 14:05 ` Mike Hearn
2014-04-07 14:15 ` Eric Martindale
2014-04-07 14:23 ` Mike Hearn
2014-04-07 19:46 ` Troy Benjegerdes
2014-04-08 3:13 ` kjj [this message]
2014-04-08 7:50 ` Mike Hearn
2014-04-09 10:38 ` Wendell
2014-04-09 11:15 ` Wladimir
2014-04-07 14:45 ` Tom Harding
2014-04-07 12:19 ` Jameson Lopp
2014-04-07 12:26 ` Pieter Wuille
2014-04-07 12:34 ` Mike Hearn
2014-04-07 12:34 ` Jameson Lopp
2014-05-20 18:38 ` Isidor Zeuner
2014-04-07 13:50 ` Gregory Maxwell
2014-04-07 13:53 ` Gregory Maxwell
2014-04-07 13:58 ` Jameson Lopp
2014-04-07 14:04 ` Gregory Maxwell
2014-04-08 11:28 ` Jesus Cea
2014-04-07 15:45 ` Justus Ranvier
2014-04-07 15:53 ` Gregory Maxwell
2014-04-07 16:02 ` Jameson Lopp
2014-04-07 16:27 ` Mark Friedenbach
2014-04-07 16:57 ` Gregory Maxwell
2014-04-07 17:01 ` Mark Friedenbach
2014-04-07 17:16 ` Gregory Maxwell
2014-04-07 17:35 ` Brent Shambaugh
2014-04-07 17:40 ` Mike Hearn
2014-04-07 17:44 ` Gregory Maxwell
2014-04-07 17:45 ` Tamas Blummer
2014-04-07 17:50 ` Justus Ranvier
2014-04-07 18:30 ` Arne Brutschy
2014-04-07 17:56 ` Brent Shambaugh
2014-04-07 17:46 ` Justus Ranvier
2014-04-07 17:39 ` Chris Williams
2014-04-07 18:23 ` Mike Hearn
2014-04-07 18:35 ` Tamas Blummer
2014-04-07 18:49 ` Gregory Maxwell
2014-04-07 19:00 ` Tamas Blummer
2014-04-07 18:48 ` Mark Friedenbach
2014-04-07 19:02 ` Gregory Maxwell
2014-04-07 19:05 ` Tamas Blummer
2014-04-07 19:03 ` Gregory Maxwell
2014-04-07 19:13 ` Tier Nolan
2014-04-07 19:20 ` Tamas Blummer
2014-04-07 19:13 ` Mark Friedenbach
2014-04-07 19:36 ` Tamas Blummer
2014-04-07 21:46 ` Ricardo Filipe
2014-04-07 19:30 ` Paul Lyon
2014-04-07 19:50 ` Tamas Blummer
2014-04-07 21:48 ` Tier Nolan
2014-04-07 21:56 ` Gregory Maxwell
2014-04-08 3:44 ` Jeff Garzik
2014-04-08 7:24 ` Jean-Paul Kogelman
2014-04-08 7:59 ` Tamas Blummer
2014-04-08 17:18 ` Andrew LeCody
2014-04-07 17:07 ` Drak
2014-05-20 8:15 ` bitcoingrant
2014-05-20 8:42 ` Mike Hearn
2014-05-20 14:37 ` Eugen Leitl
2014-05-20 14:52 ` Gmail
2014-05-20 18:46 ` Andy Alness
2014-05-20 19:17 ` Jeff Garzik
2014-05-20 20:09 ` Andy Alness
2014-05-20 20:22 ` Jeff Garzik
2014-04-07 21:55 Paul Lyon
2014-04-07 22:14 ` Tier Nolan
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=53436977.4030808@jerviss.org \
--to=bitcoin-devel@jerviss.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=eric@ericmartindale.com \
/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