From: Sergio Demian Lerner <sergio.d.lerner@gmail.com>
To: Tamas Blummer <tamas@bitsofproof.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 18:12:17 -0300 [thread overview]
Message-ID: <CAKzdR-pzW-0eCeR06oyhmzDKM8csLzXj9T33uKqxLQ0FicMWSw@mail.gmail.com> (raw)
In-Reply-To: <0CC6B26F-AB95-423A-B6D3-5852BD2863AA@bitsofproof.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
Hector,
I can only say 2 things in the brief time I have now:
1. There is a solution that I proposed for proving you own a copy of the
block-chain. It's using aymmetric-time functions:
https://bitslog.wordpress.com/2014/11/03/proof-of-local-blockchain-storage/
2. I'm finishing a paper on a transaction system (DAGCoin) which relies on
proof-of-work per transactions, and no per blocks. Actually it has no
blocks.
This has been explored in the past, but I came up with some basic ideas
that make this work a few months ago. I will forward a draft to you while
at the same time I try to analyze your proposal. Or I may publish the draft
altogether.
Best regards,
Sergio
On Fri, Aug 21, 2015 at 5:50 PM, Tamas Blummer via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 3897 bytes --]
prev parent reply other threads:[~2015-08-21 21:12 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
2015-08-21 21:12 ` Sergio Demian Lerner [this message]
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=CAKzdR-pzW-0eCeR06oyhmzDKM8csLzXj9T33uKqxLQ0FicMWSw@mail.gmail.com \
--to=sergio.d.lerner@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tamas@bitsofproof.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