public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jameson Lopp <jameson.lopp@gmail.com>
To: Hector Chu <hectorchu@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: Wed, 19 Aug 2015 08:08:13 -0400	[thread overview]
Message-ID: <CADL_X_dUd2MLt_P5+o=uS+LP_12ybRTGeq1WQzQY2m6kf6qtDA@mail.gmail.com> (raw)
In-Reply-To: <CAAO2FKE44WqJOEaR2TYRwzAsPQxh7Z1K3esQiMFsSsk2+65-4w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

If operating as an SPV node then it can check the transactions by querying
other nodes.

On an unrelated note, it sounds like your proposal will significantly
increase the data size of every transaction, which will create even more
contention for block space.

- Jameson

On Wed, Aug 19, 2015 at 7:48 AM, Hector Chu <hectorchu@gmail.com> wrote:

> On 19 August 2015 at 12:42, Jameson Lopp <jameson.lopp@gmail.com> wrote:
> > If you can actually come up with a technical solution that allows for a
> node
> > operator to prove to the rest of the network that they are running an
> honest
> > full node that hosts the entire blockchain, then you can move forward
> with a
> > direct monetary incentivization proposal. To my knowledge no one has been
> > successful in that endeavor. To be more clear, your proposal would need
> to
> > be able to differentiate between a full node and a pseudonode.
> > https://github.com/basil00/PseudoNode
>
> The proof is in the validation of transactions. How can a node
> reliably validate transactions unless it has the past history of
> transactions? Entire blockchain not required or necessary, but that's
> a plus.
>

[-- Attachment #2: Type: text/html, Size: 1707 bytes --]

  reply	other threads:[~2015-08-19 12:08 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 [this message]
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

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='CADL_X_dUd2MLt_P5+o=uS+LP_12ybRTGeq1WQzQY2m6kf6qtDA@mail.gmail.com' \
    --to=jameson.lopp@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=hectorchu@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