From: Tamas Blummer <tamas@bitsofproof.com>
To: Jameson Lopp <jameson.lopp@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A solution to increase the incentive of running a node
Date: Fri, 21 Aug 2015 22:50:58 +0200 [thread overview]
Message-ID: <0CC6B26F-AB95-423A-B6D3-5852BD2863AA@bitsofproof.com> (raw)
In-Reply-To: <CADL_X_duSHosyMAfOXPv7WcWKTY19Q2i+_zFSuuGbGantbbmRw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
Jameson,
I like your thinking about the implicit reward of full nodes. It was not perceived as sufficient by many, hence full node counts were falling.
This might reverse now as the implicit value of validating yourself however becomes higher in a heterogenous environment, that is if there are hard forks in the wild.
Actually pooled mining became an option through the homogenous nature of the network.
Tamas Blummer
> On Aug 19, 2015, at 13:42, Jameson Lopp via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> The incentives for running a node may not be obvious to the average user, but they are there. Rather than direct monetary incentives, they are indirect. For one, it allows you to have a local copy of the blockchain that you validated yourself - trustlessness is the entire point of this system. Having local self-validated blockchain data is also essential for any enterprise that needs to quickly access large volumes of it. The other incentive is it supports the network. Users may feel that this is necessary out of altruism or they may feel incentivized to protect their investments in Bitcoin.
[-- Attachment #1.2: Type: text/html, Size: 2669 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-08-21 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 11:15 [bitcoin-dev] A solution to increase the incentive of running a node Hector Chu
2015-08-19 11:42 ` Jameson Lopp
2015-08-19 11:48 ` Hector Chu
2015-08-19 12:08 ` Jameson Lopp
2015-08-19 12:15 ` Hector Chu
2015-08-19 12:44 ` Jameson Lopp
2015-08-19 12:51 ` Hector Chu
2015-08-21 20:50 ` Tamas Blummer [this message]
2015-08-21 21:12 ` Sergio Demian Lerner
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=0CC6B26F-AB95-423A-B6D3-5852BD2863AA@bitsofproof.com \
--to=tamas@bitsofproof.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jameson.lopp@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