public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@exmulti.com>
To: Oliver Egginger <bitcoin@olivere.de>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DOS-Attacks on bitcoin-client?
Date: Mon, 8 Apr 2013 01:42:39 -0400	[thread overview]
Message-ID: <CA+8xBpcSpi2ZKYb5wLTO45BW02213zWykJ9_z26cde7gZKvF_A@mail.gmail.com> (raw)
In-Reply-To: <51618612.9010603@olivere.de>

BTW, check out the blockchain torrent, as one way of offloading some
of the download bandwidth used from the P2P network:

     Bitcoin blockchain data torrent
     https://bitcointalk.org/index.php?topic=145386.0

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com



      parent reply	other threads:[~2013-04-08  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 14:43 [Bitcoin-development] DOS-Attacks on bitcoin-client? Oliver Egginger
2013-04-07 15:22 ` Scott Howard
2013-04-07 16:35   ` Oliver Egginger
2013-04-08  5:42 ` Jeff Garzik [this message]

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=CA+8xBpcSpi2ZKYb5wLTO45BW02213zWykJ9_z26cde7gZKvF_A@mail.gmail.com \
    --to=jgarzik@exmulti.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=bitcoin@olivere.de \
    /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