From: "NxtChg" <nxtchg@hush•com>
To: "Eric Voskuil" <eric@voskuil•org>,
"Peter Todd" <pete@petertodd•org>,
"Matt Corallo" <lf-lists@mattcorallo•com>
Cc: Bitcoin development mailing list
<bitcoin-dev@lists•linuxfoundation.org>,
Libbitcoin <libbitcoin@lists•dyne.org>
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
Date: Sat, 19 Sep 2015 10:27:14 +0300 [thread overview]
Message-ID: <20150919072714.D3349404B9@smtp.hushmail.com> (raw)
In-Reply-To: <55FD0737.1080008@voskuil.org>
>The state is the threat in the Bitcoin threat model. You comments below
>acknowledge it. The assumption of hostile state actors is the only
>rational starting point. That which is regulated (and regulatable)
>in Bitcoin is the attack surface.
I think, you just proved my point. If your goal is to shrink the attack surface as much as possible,
you are better off being a marginalized alt-coin.
>This threat represents the difference between Bitcoin and Fedcoin.
_This_ is the false dichotomy. There's a range of coins between DarkCoin and FedCoin.
>This is extremely naive. At a minimum, getting popular/successful (and regulated) is the formula for regulatory capture.
Let me give you an example.
Suppose you are a regular guy, say Peter Todd, and you are faced with 10 policemen in anti-riot gear.
You can fight them in two ways:
1. become stronger, so you could provide an adequate response, either by turning into Hulk or by getting another 30-50 Peter Todds.
2. lose some fat, learn a few parkour tricks and move around mostly by night behind dumpsters.
The worst you can fare is just being Peter Todd with a backpack and an expensive camera on his neck, wandering around the city in daylight.
Your vision of Bitcoin is the most vulnerable to government attacks.
next prev parent reply other threads:[~2015-09-19 7:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:32 Jeff Garzik
2015-09-16 21:51 ` Matt Corallo
2015-09-18 5:55 ` Mark Friedenbach
2015-09-18 17:10 ` Dave Scotese
2015-09-18 17:28 ` Eric Lombrozo
2015-09-18 20:06 ` Matt Corallo
2015-09-18 22:33 ` Mike Hearn
2015-09-19 16:03 ` cipher anthem
2015-09-19 20:43 ` Mike Hearn
2015-09-19 1:47 ` Peter Todd
2015-09-19 6:06 ` NxtChg
2015-09-19 6:56 ` Eric Voskuil
2015-09-19 7:27 ` NxtChg [this message]
2015-09-19 7:39 ` Eric Voskuil
2015-09-19 7:57 ` NxtChg
2015-09-19 8:52 ` Eric Voskuil
2015-09-19 13:32 ` NxtChg
2015-09-19 20:57 ` Mike Hearn
2015-09-19 21:53 ` phm
2015-09-20 1:26 ` Dave Scotese
2015-09-20 2:18 ` Milly Bitcoin
2015-09-20 9:18 ` NxtChg
2015-09-20 9:25 ` Mike Hearn
2015-09-20 15:43 ` Mark Friedenbach
2015-09-20 16:21 ` NxtChg
2015-09-20 16:34 ` Milly Bitcoin
2015-09-20 20:23 ` Steven Pine
2015-09-20 20:54 ` Milly Bitcoin
2015-09-20 21:33 ` s7r
2015-09-20 21:45 ` Eric Lombrozo
2015-09-20 22:02 ` Milly Bitcoin
2015-09-20 22:21 ` Eric Lombrozo
2015-09-20 22:51 ` Milly Bitcoin
2015-09-20 23:11 ` Eric Lombrozo
2015-09-21 0:11 ` Dave Scotese
2015-09-21 5:04 ` Corey Haddad
2015-09-21 11:45 ` Milly Bitcoin
2015-09-21 8:48 ` NxtChg
2015-09-20 21:10 ` NxtChg
2015-09-20 21:13 ` Steven Pine
2015-09-20 21:34 ` Milly Bitcoin
2015-09-20 21:24 ` Milly Bitcoin
2015-09-20 21:16 ` Eric Lombrozo
2015-09-21 10:30 ` Mike Hearn
2015-09-18 22:15 ` [bitcoin-dev] Improving Blocksize Communication Through Markets Paul Sztorc
2015-09-20 11:41 ` Isidor Zeuner
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=20150919072714.D3349404B9@smtp.hushmail.com \
--to=nxtchg@hush$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=eric@voskuil$(echo .)org \
--cc=lf-lists@mattcorallo$(echo .)com \
--cc=libbitcoin@lists$(echo .)dyne.org \
--cc=pete@petertodd$(echo .)org \
/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