public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Brent Shambaugh <brent.shambaugh@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Date: Mon, 7 Apr 2014 19:40:17 +0200	[thread overview]
Message-ID: <CANEZrP3_v2zAqMkcTtQ1Mys2rUEcsd_MpLySefpgJ-P7OSg34g@mail.gmail.com> (raw)
In-Reply-To: <CACvcBVq2+37jWgxBg2Zjj6KFtT1ZnZzTa7FOw1sLwimeT0ahhA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2863 bytes --]

It uses ~no electricity, it's not like mining.

The primary resources it needs are disk space and bandwidth, after an
intensive initial day or two of building the database.

Actually, I wonder if we should start shipping (auditable) pre-baked
databases calculated up to the last checkpoint so people can download them
and boot up their node right away. Recalculating the entire thing from
scratch every time isn't sustainable in the long run anyway.


On Mon, Apr 7, 2014 at 7:35 PM, Brent Shambaugh
<brent.shambaugh@gmail.com>wrote:

> How difficult would it be to set up a node? Using lots of electricity at
> home (if required) could be an issue, but I do have a Webfaction account.
>
>
> On Mon, Apr 7, 2014 at 12:16 PM, Gregory Maxwell <gmaxwell@gmail.com>wrote:
>
>> On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach <mark@monetize.io>
>> wrote:
>> > On 04/07/2014 09:57 AM, Gregory Maxwell wrote:
>> >> That is an implementation issue— mostly one that arises as an indirect
>> >> consequence of not having headers first and the parallel fetch, not a
>> >> requirements issue.
>> >
>> > Oh, absolutely. But the question "why are people not running full
>> > nodes?" has to do with the current implementation, not abstract
>> > capabilities of a future version of the bitcoind code base.
>>
>> The distinction is very important because it's a matter of things we
>> can and should fix vs things that cannot be fixed except by changing
>> goals/incentives!  Opposite approaches to handling them.
>>
>> When I read "resource requirements of a full node are moving beyond" I
>> didn't extract from that that "there are implementation issues that
>> need to be improved to make it work better for low resource users" due
>> to the word "requirements".
>>
>>
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 4236 bytes --]

  reply	other threads:[~2014-04-07 17:40 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
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 [this message]
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=CANEZrP3_v2zAqMkcTtQ1Mys2rUEcsd_MpLySefpgJ-P7OSg34g@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=brent.shambaugh@gmail.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