From: "NxtChg" <nxtchg@hush•com>
To: moonpunter@gmail•com,
"bitcoin-dev" <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
Date: Sun, 20 Sep 2015 12:18:21 +0300 [thread overview]
Message-ID: <20150920091822.2D4D8404BA@smtp.hushmail.com> (raw)
In-Reply-To: <55FDD951.9010709@gmail.com>
>Bitcoin does not enjoy nearly the popularity that marijuana and guns do,
Marijuana is an individual activity. Precisely the problem with Bitcoin you envision, where each one of us could be easily jailed.
Guns are quite different: they have NRA and judging by how successful it is at fending _any_ sort of gun control laws, it can very effectively counter-balance the government.
If Bitcoin had it's own NBitA, it would be in a much better position to defend itself than a bunch of individual users.
>A mining network that anyone can contribute to would enable Bitcoin to stay alive in spite of this
Again. Start building an alt-coin with ASIC-resistant algorithm then, it's much more important than the small blocks in your model.
And it must also have other features to support your fight: integrated darkcoin-style anonymity, only TOR as the protocol, etc.
Trying to use Bitcoin, which is overly-exposed, for this kind of fight is a pretty dumb idea.
You won't have the benefits of a small attack surface and you won't have the benefits of strength - the most vulnerable position.
Not to mention that many people simply don't share your vision of Bitcoin as a marginalized outlawed coin somewhere in the depths of TOR.
Looking at how enthusiastically people in smallblockistan promote the most vulnerable position, I'd say they are all agents of USG.
next prev parent reply other threads:[~2015-09-20 9:18 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
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 [this message]
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=20150920091822.2D4D8404BA@smtp.hushmail.com \
--to=nxtchg@hush$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=moonpunter@gmail$(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