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:51:14 +0100 [thread overview]
Message-ID: <CAAO2FKFz7kSzkB58aAqYPNe8kh8Oe0oVqxXweq9KhHKae4frpA@mail.gmail.com> (raw)
In-Reply-To: <CADL_X_f5WZOQF==1LiBkX=kLO+9dGb1mxu__6Mu_b1WqR20hYA@mail.gmail.com>
On 19 August 2015 at 13:44, Jameson Lopp <jameson.lopp@gmail•com> wrote:
> It's possible to check that a transaction is cryptographically valid without
> having any blockchain data available; are you referring to a different type
> of validation?
It seems laborious to enumerate all the validations that are performed
on a transaction before it can be mined into a block, but for starters
we need to check it isn't a double-spend, and that its signatures
satisfy the outputs' pubkeys.
> If you're running an SPV node that is listening to full nodes on the
> network, you can request an unconfirmed transaction from connected peers
> after receiving the inventory message they send - that's how unconfirmed
> transactions propagate through the node network. This is not 100% proof that
> the transaction is valid for inclusion in the blockchain, but it's a very
> good indicator.
If you as an SPV node are waiting for unconfirmed transactions to be
relayed to you, you are going to have a slow start in mining those
transactions, decreasing the likelihood of receiving the mining
reward. Nodes should accept the first POW for a transaction and
discard any subsequent ones received.
next prev parent reply other threads:[~2015-08-19 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 11:15 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 [this message]
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=CAAO2FKFz7kSzkB58aAqYPNe8kh8Oe0oVqxXweq9KhHKae4frpA@mail.gmail.com \
--to=hectorchu@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jameson.lopp@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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