public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Hector Chu <hectorchu@gmail.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: Wed, 19 Aug 2015 13:15:48 +0100	[thread overview]
Message-ID: <CAAO2FKHG1PHKjMw7ER=w-MgS7uNY_NLgzFM0aVKqP+BRUZOw9g@mail.gmail.com> (raw)
In-Reply-To: <CADL_X_dUd2MLt_P5+o=uS+LP_12ybRTGeq1WQzQY2m6kf6qtDA@mail.gmail.com>

On 19 August 2015 at 13:08, Jameson Lopp <jameson.lopp@gmail.com> wrote:
> If operating as an SPV node then it can check the transactions by querying
> other nodes.

SPV is for checking validity of transactions that have already entered
the blockchain, as I understand it. My proposal requires nodes to
validate transactions that are unconfirmed, and to commit to the
validation by doing a POW on it.

> 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.

If we stipulate that the coinbase fields only hold space for a single
pubkey, then the entire block header including the two coinbases
should only take an extra 100 bytes or so. Transactions are already
routinely 250 bytes+. So an increase of roughly 33%.


  reply	other threads:[~2015-08-19 12:16 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 [this message]
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='CAAO2FKHG1PHKjMw7ER=w-MgS7uNY_NLgzFM0aVKqP+BRUZOw9g@mail.gmail.com' \
    --to=hectorchu@gmail.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