📅 Original date posted:2014-04-07
📝 Original message: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 at 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 at gmail.com>wrote:
>
>> On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach <mark at 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 at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/5ce1e052/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:17:46
in reply to nevent1q…dgdv
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydSeen on
wss://relay.noswhere.comPublished at
2023-06-07 15:17:46Event JSON
{
"id": "edabccdddf26e0e1b27c93b3b6e2ef7e0fdedc90bdfd86d3c9300313fa1393b2",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151066,
"kind": 1,
"tags": [
[
"e",
"376923b22263ee9091876d1ae02202112b3aeaa7a25d30e967b871af6956d76a",
"",
"root"
],
[
"e",
"833c9b0e3b03a07197d2f51dda6c973f60f98c2cfd7cf27ec19b697942ef3048",
"",
"reply"
],
[
"p",
"aadf522541533786ae1dad10bc217d5d86ae1721ebcfa3a0821c7849f35d3ba5"
]
],
"content": "📅 Original date posted:2014-04-07\n📝 Original message:It uses ~no electricity, it's not like mining.\n\nThe primary resources it needs are disk space and bandwidth, after an\nintensive initial day or two of building the database.\n\nActually, I wonder if we should start shipping (auditable) pre-baked\ndatabases calculated up to the last checkpoint so people can download them\nand boot up their node right away. Recalculating the entire thing from\nscratch every time isn't sustainable in the long run anyway.\n\n\nOn Mon, Apr 7, 2014 at 7:35 PM, Brent Shambaugh\n\u003cbrent.shambaugh at gmail.com\u003ewrote:\n\n\u003e How difficult would it be to set up a node? Using lots of electricity at\n\u003e home (if required) could be an issue, but I do have a Webfaction account.\n\u003e\n\u003e\n\u003e On Mon, Apr 7, 2014 at 12:16 PM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003ewrote:\n\u003e\n\u003e\u003e On Mon, Apr 7, 2014 at 10:01 AM, Mark Friedenbach \u003cmark at monetize.io\u003e\n\u003e\u003e wrote:\n\u003e\u003e \u003e On 04/07/2014 09:57 AM, Gregory Maxwell wrote:\n\u003e\u003e \u003e\u003e That is an implementation issue— mostly one that arises as an indirect\n\u003e\u003e \u003e\u003e consequence of not having headers first and the parallel fetch, not a\n\u003e\u003e \u003e\u003e requirements issue.\n\u003e\u003e \u003e\n\u003e\u003e \u003e Oh, absolutely. But the question \"why are people not running full\n\u003e\u003e \u003e nodes?\" has to do with the current implementation, not abstract\n\u003e\u003e \u003e capabilities of a future version of the bitcoind code base.\n\u003e\u003e\n\u003e\u003e The distinction is very important because it's a matter of things we\n\u003e\u003e can and should fix vs things that cannot be fixed except by changing\n\u003e\u003e goals/incentives! Opposite approaches to handling them.\n\u003e\u003e\n\u003e\u003e When I read \"resource requirements of a full node are moving beyond\" I\n\u003e\u003e didn't extract from that that \"there are implementation issues that\n\u003e\u003e need to be improved to make it work better for low resource users\" due\n\u003e\u003e to the word \"requirements\".\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e Put Bad Developers to Shame\n\u003e\u003e Dominate Development with Jenkins Continuous Integration\n\u003e\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140407/5ce1e052/attachment.html\u003e",
"sig": "35c70672b0ab8b6cdc35679a3c92e00b0fc459766114bce546b96f52b8fc94bb8d70fe4d86bc5cde19753263f4dcdccd3b5a6a50c59320080a0d9d8f3f9908ef"
}