Re: [Bitcoin-development] Why are we bleeding nodes?
Okay awesome. It seems like I set up a Litecoin node without knowing it (because it was like this: https://bitcointalk.org/index.php?topic=128122.0) I was able to bootstrap it (https://litecoin.info/). On Mon, Apr 7, 2014 at 12:40 PM, Mike Hearn wrote: > 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 >> >> > -- 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
Re: [Bitcoin-development] Why are we bleeding nodes?
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
[Bitcoin-development] Bitcoin for W3C Payments Workshop, March 24-25
Hello Bitcoiners, I have been working on some use cases for the W3C payments workshop. I'd like to include Bitcoin, but I might not have the time: Here is what I have: https://www.w3.org/community/webpayments/wiki/WebPaymentsMobileUseCases Which is editable with a w3c username and password. Just be a member of the webpayments community group: http://www.w3.org/community/webpayments/ More formally you can submit a pull request to: https://github.com/w3c-webmob/payments-use-cases - Due to discussions with others am attempting to apply the following template: Name: name of the solution Use Cases: Key use cases for the solution Regions and currencies: Any SDKs or APIs which are available to developers with the following things to consider (for use cases): (1) add real money to the service (2) buy a physical good in the real wold (e.g., a cup of coffee) (3) pay for physical service (e.g., gym membership)? (4) convert virtual money back into paper money (5) transfer money from one person to another (even if the second person is not signed up for the service)? (6) buy product online (7) resolve disputes? (8) view transactions? (9) secure the wallet (10) etc. Thanks for your time and have a great day! -Brent Shambaugh -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development