public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Tamas Blummer <tamas@bitsofproof•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV	wallets
Date: Wed, 09 Apr 2014 14:04:46 -0400	[thread overview]
Message-ID: <1fa234ec-9dd4-45de-8ac8-ca20a158c344@email.android.com> (raw)
In-Reply-To: <0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



On 9 April 2014 13:50:03 GMT-04:00, Tamas Blummer <tamas@bitsofproof•com> wrote:
>Block header has to be available in SPV and also in an UTXO only
>storing core node, so why not serve it if bandwith allows.
>
>Serving any additional information like known peer adresses or known
>full blocks is certainly beneficial and should be offered if at hand.

Big security advantages too. For instance if an attacker hacks, say, 10℅ of hashing power the next step for them to attack SPV clients is to try to Sybil attack them so they won't find out about the longer chain. The fewer providers of block chain data there are out there the easier that attack is - just simultaneously DoS a bunch of nodes, perhaps by a low-bandwidth exploit like the bloom io or division by zero DoS attacks. This is much harder to pull off if every SPV client is passing around block headers.

Similarly by passing around full blocks the attacker has a harder time knocking other miners off the network. Regardless of whether or not a miner's peers are fully validating chain data they still have the data they need to mine the next block and thus extend the longest correct chain.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1

iQFQBAEBCgA6BQJTRYu+MxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwheuQCADUyClLOLP1xpG1000l
uzcfPTZuIXTpzOAmYHKs/MSb6mph/Shsu0/94eW7npQNSVeZC8wQQZ1oFQ9j1GJc
SKViYJfn5yMdNvMkaWazhC0r3jxxF0AI7oy2KlnSjasfczfOQuYICJadTCwvUHrb
GrKVDbgsKNzZYYKn86vF4hsLwtJN4moeqX85TYN1DC7//7hgNywA73Xt2/gdwfqe
LOsD4nS7mUQObQd6TcLwXDDNEGTrdS572jdYH5sykwZjPH+wqwcm2WKTnIULsJR0
OwGUi505AKJJnLcEmZ/kGbCmKB+xJ5kExjlExtcUPrJlc+xqubhnnGCMjBiGCXSY
kYCK
=HXRZ
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2014-04-09 18:05 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 15:29 Wladimir
2014-04-09 15:37 ` Tamas Blummer
2014-04-09 15:41 ` Natanael
2014-04-09 15:54   ` Gregory Maxwell
2014-04-09 16:09     ` Thomas Voegtlin
2014-04-09 19:25       ` Wladimir
2014-04-10  6:04         ` Tamas Blummer
2014-04-10 11:09           ` Wladimir
2014-04-10 11:29             ` Mike Hearn
2014-04-10 11:32             ` Pieter Wuille
2014-04-10 11:43               ` Peter Todd
2014-04-10 11:50               ` Gregory Maxwell
2014-04-10 11:54                 ` Peter Todd
2014-04-10 17:30                   ` Tier Nolan
2014-04-11 16:54                     ` Gregory Maxwell
2014-05-04 21:11                       ` Tier Nolan
2014-04-09 17:31   ` Wladimir
2014-04-09 15:42 ` Brian Hoffman
2014-04-09 15:57   ` Gregory Maxwell
2014-04-09 16:09     ` Tamas Blummer
2014-04-09 15:47       ` Mark Friedenbach
2014-04-09 16:27         ` Tamas Blummer
2014-04-09 17:46           ` Peter Todd
2014-04-09 17:50             ` Tamas Blummer
2014-04-09 18:00               ` Mike Hearn
2014-04-09 18:19                 ` Wladimir
2014-04-09 18:35                   ` Justus Ranvier
2014-04-09 18:46                     ` Wladimir
2014-04-09 18:50                     ` Gregory Maxwell
2014-04-09 18:58                       ` Justus Ranvier
2014-04-09 19:33                         ` Gregory Maxwell
2014-04-09 20:12                           ` slush
2014-04-09 20:31                             ` slush
2014-04-09 20:36                               ` Mark Friedenbach
2014-04-09 21:04                                 ` Gregory Maxwell
2014-04-09 20:37                               ` Wladimir
2014-04-09 20:35                             ` Wladimir
2014-04-09 20:50                               ` slush
2014-04-09 20:55                             ` Laszlo Hanyecz
2014-04-10  6:38                             ` Mike Hearn
2014-04-10  6:50                               ` Wladimir
2014-04-10  7:09                                 ` Mike Hearn
2014-04-10  9:33                                   ` Peter Todd
2014-04-10  7:10                                 ` Tamas Blummer
2014-04-10  9:17                                   ` Mike Hearn
2014-04-10  9:39                                     ` Tamas Blummer
2014-04-10 10:40                                       ` Mike Hearn
2014-04-10 10:44                                         ` Tamas Blummer
2014-04-10 11:36                                           ` Peter Todd
2014-04-10 11:45                                             ` Mike Hearn
2014-04-10 11:52                                               ` Peter Todd
2014-04-10  9:47                                     ` Peter Todd
2014-04-09 18:04               ` Peter Todd [this message]
     [not found]   ` <CA+s+GJBpvqqu=XEojyekx5su+JfYLwz+zsbo8L0=5t6s-_b33w@mail.gmail.com>
2014-04-09 17:35     ` [Bitcoin-development] Fwd: " Wladimir
2014-04-09 16:03 ` [Bitcoin-development] " Peter Todd
2014-04-09 17:33   ` Alex Mizrahi
2014-04-09 17:38     ` Wladimir
2014-04-09 17:38     ` Peter Todd
2014-04-09 18:35 ` Kevin

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=1fa234ec-9dd4-45de-8ac8-ca20a158c344@email.android.com \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=tamas@bitsofproof$(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