From: Tier Nolan <tier.nolan@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [ANN] High-speed Bitcoin Relay Network
Date: Wed, 6 Nov 2013 12:25:31 +0000 [thread overview]
Message-ID: <CAE-z3OXQiT-6OXddb9_jpY2Qqbfs+BKAVv3M-rQ4eedwBS2MAg@mail.gmail.com> (raw)
In-Reply-To: <5279D89D.5000609@bluematt.me>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Wed, Nov 6, 2013 at 5:50 AM, Matt Corallo <bitcoin-list@bluematt•me>wrote:
> Relay node details:
> * The relay nodes do some data verification to prevent DoS, but in
> order to keep relay fast, they do not fully verify the data they are
> relaying, thus YOU SHOULD NEVER mine a block building on top of a
> relayed block without fully checking it with your own bitcoin validator
> (as you would any other block relayed from the P2P network).
>
Wouldn't this cause disconnects due to misbehavior?
A standard node connecting to a relay node would receive
blocks/transactions that are not valid in some way and then disconnect.
Have you looked though the official client to find what things are
considered signs that a peer is hostile? I assume things like double
spending checks count as misbehavior and can't be quickly checked by a
relay node.
Maybe another bit could be assigned in the services field as "relay". This
means that the node doesn't do any checking.
Connects to relay nodes could be command line/config file only. Peers
wouldn't connect to them.
[-- Attachment #2: Type: text/html, Size: 1518 bytes --]
next prev parent reply other threads:[~2013-11-06 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 5:50 Matt Corallo
2013-11-06 9:23 ` Mike Hearn
2013-11-06 11:42 ` Jeff Garzik
2013-11-06 12:25 ` Tier Nolan [this message]
2013-11-06 23:35 ` Matt Corallo
2013-11-08 11:46 ` Mike Hearn
2013-11-14 2:11 ` Matt Corallo
2013-11-13 20:13 ` John Dillon
2013-11-14 2:14 ` Matt Corallo
2014-08-03 0:56 ` Matt Corallo
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=CAE-z3OXQiT-6OXddb9_jpY2Qqbfs+BKAVv3M-rQ4eedwBS2MAg@mail.gmail.com \
--to=tier.nolan@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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