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 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 wrote: > >> On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach >> 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 > >