public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ryan Carboni <ryan.jc.pc@gmail•com>
To: Mark Friedenbach <mark@monetize•io>,
	bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin difficulty sanity check suggestion
Date: Mon, 23 Dec 2013 23:37:32 -0800	[thread overview]
Message-ID: <CAO7N=i1DpGnfjgAX6GHNC-yVq_9P38vb_1MszcRcRhEA8nnLcA@mail.gmail.com> (raw)
In-Reply-To: <52B8EB37.2080006@monetize.io>

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

It does take a state-level actor to apparently disconnect *multiple *miners
from the rest of the network.

How many Bitcoin miners hash an entire percent or more of the Bitcoin
network? What you're proposing is an attack at the highest levels of the
internet infrastructure.


On Mon, Dec 23, 2013 at 6:02 PM, Mark Friedenbach <mark@monetize•io> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Which would leave you entirely in the hands of your dialup provider.
> Or the manufacturer of your switch. Or your ISP's backbone provider.
> It does not take a state-level actor to do network attacks.
>
> BTW, what does "difficulty would be reset" mean? There are multiple
> ways to interpret that statement. In the most straightforward way, my
> objections apply.
>
> On 12/23/2013 05:51 PM, Ryan Carboni wrote:
> > I think you misunderstood my statement. If time > 3 days, and after
> > 4 blocks have been mined, then difficulty would be reset.
> >
> > In theory, one would have to isolate roughly one percent of the
> > Bitcoin network's hashing power to do so. Which would indicate an
> > attack by a state actor as opposed to anything else. Arguably, the
> > safest way to run Bitcoin is through a proprietary dial-up
> > network.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJSuOs3AAoJEAdzVfsmodw4BwAP/0Ynq/SxNIBFFdL7RaSiE5KM
> zNRtlZJCYvmCXgKKtMyO+Ron+YGqY8yg8r0ifb6oqlJCG5t0msExym/CA9CYMV6V
> UnVaGaNkFrLSF1q8Dt6X4I9OSeCiBstahQOjPaerUycLTY2W/cKPblhCC0rvXrfI
> 3Fz3p6SHbCcNHw89w6ry3QG420+UNroFCpNu+Oa2YfWoZY2p91JLbuiUwXL5KEac
> PDskHGsb9q1vyAkCJ6eOp3MJfFP/Dy7mASVwPql/nzf2ceSDtO4dpngo0uNsCwFo
> QSWIRdWv4OiJk1OM6fjEj/51mebczgO0ShczRKk9QkX4FEFEqP/ARdbl8bSC4IsT
> /3s2HHiYDahEOMiXV5ao3kmBpyUR8p4erRbtwRzdZzOgGL37yxj8VGmY93bkVQNB
> zi2n3WCCju0a+gqREyaEFAM8kPIhx9++YNIddwQxK38njUSe2CzqM8t+28ZfseYl
> YnQeNFUfcmvzhxTXxgyoCuGF5HbFRTn/AallkYSPxYtxGq4WuLN36BS3cTv8wCLz
> sYTyuxWxjZ7CS8fx8MWilw72tQf9torwmrWJtjgRLFE3OvQxRjN+ppDV8cfC8UAB
> p0CGzBgVaw5yZ5LzCawQVTGWJdzs+ZPlQu8SO53dHhEtRAmdbFa0mMD2FrS/5Ih/
> YcwdP6Xm69HTgzCenu5F
> =HtRS
> -----END PGP SIGNATURE-----
>

[-- Attachment #2: Type: text/html, Size: 2901 bytes --]

  parent reply	other threads:[~2013-12-24  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  3:10 Ryan Carboni
2013-12-23  3:22 ` Mark Friedenbach
2013-12-23 20:22   ` Robin Ranjit Singh Chauhan
2013-12-24  1:51   ` Ryan Carboni
2013-12-24  4:05     ` Allen Piscitello
2013-12-24  7:41       ` Ryan Carboni
2013-12-24  7:53         ` Gavin Costin
     [not found]     ` <52B8EB37.2080006@monetize.io>
2013-12-24  7:37       ` Ryan Carboni [this message]
2013-12-24  8:34     ` 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='CAO7N=i1DpGnfjgAX6GHNC-yVq_9P38vb_1MszcRcRhEA8nnLcA@mail.gmail.com' \
    --to=ryan.jc.pc@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=mark@monetize$(echo .)io \
    /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