public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "G. Andrew Stone" <g.andrew.stone@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A compromise between BIP101 and Pieter's proposal
Date: Fri, 31 Jul 2015 14:04:53 -0400	[thread overview]
Message-ID: <CAHUwRvuN=xg527QFs8s6MmGOhTYbUKt0u3QHf6sKw7Ywi5KDTw@mail.gmail.com> (raw)
In-Reply-To: <CAGLBAhc4Yxhrdd07nt6pY7fo7BmXXgcxANq++w=WfSoUA5NfBA@mail.gmail.com>

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

There's a large array of solutions that are bigger than the cheapest home
broadband, but smaller then renting hardware in a data center.  Every
company with internet service to their location purchases one of these
options.  If Bitcoin full node bandwidth requirements ever exceed a
hobbyist's reach, s/he can always pool resources with other individuals to
purchase one of these solutions, and a 1-room office.

How many of you have connected to multiple ISPs and are routing internet
traffic between them?  But TCP is still permissionless.

Bitcoin node requirements will grow beyond a hobbyist reach (but not that
of the garage entrepreneur).   The truth is that as technologies grow and
mature, the hobbyists move on but anyone who has a real reason to continue
using it stays.  This fact does not destroy its decentralization.

I do not think that reasonable scaling will significantly affect full node
quantity (historical downtrends are conflated with the simultaneous
transition from hobbyist to professional).

At the same time the ability to create an independent full node is a
tremendous force keeping existing full nodes honest -- this potential is
more powerful then the fact.

Which would you choose, a 10 thousand node strong bankCoin, or a 1000 node
open source permissionless Bitcoin?


On Fri, Jul 31, 2015 at 12:22 PM, Dave Scotese via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Here are some books that will help more people understand why Adam's
> concern is important:
> Kicking the Dragon (by Larken Rose)
> The State (by Franz Oppenheimer)
>
> Like he said, it isn't much about bitcoin.  Our crypto is just one of the
> defenses we've created, and understanding what it defends will help us
> maintain its value.
>
> Dave
>
> On Fri, Jul 31, 2015 at 6:16 AM, Adam Back via bitcoin-dev <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>>
>> I think trust the data-center logic obviously fails, and I was talking
>> about this scenario in the post you are replying to.  You are trusting the
>> data-center operator period.  If one could trust data-centers to run
>> verified code, to not get hacked, filter traffic, respond to court orders
>> without notifying you etc that would be great but that's unfortunately not
>> what happens.
>>
>> Data-center operators are bound to follow laws, including NSLs and gag
>> orders.  They also get hacked, employ humans who can be corrupt,
>> blackmailed, and themselves centralisation points for policy attack.
>> Snowden related disclosures and keeping aware of security show this is very
>> real.
>>
>> This isn't much about bitcoin even, its just security reality for hosting
>> anything intended to be secure via decentralisation, or just hosting in
>> general while at risk of political or policy attack.
>>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

  reply	other threads:[~2015-07-31 18:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  8:39 [bitcoin-dev] A compromise between BIP101 and Pieter's proposal jl2012
2015-07-31 10:16 ` Adam Back
2015-07-31 13:07   ` jl2012
2015-07-31 13:17     ` Adam Back
2015-07-31 16:22       ` Dave Scotese
2015-07-31 18:04         ` G. Andrew Stone [this message]
2015-07-31 13:12   ` Ivan Brightly
2015-08-01 20:45 ` Pieter Wuille
2015-08-01 23:57   ` Tom Harding
2015-08-02  7:16   ` jl2012
2015-08-02  8:03     ` odinn
2015-08-02 10:32     ` Pieter Wuille
2015-08-02 10:38       ` Venzen Khaosan
2015-08-02 22:07         ` Dave Scotese

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='CAHUwRvuN=xg527QFs8s6MmGOhTYbUKt0u3QHf6sKw7Ywi5KDTw@mail.gmail.com' \
    --to=g.andrew.stone@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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