From: odinn <odinn.cyberguerrilla@riseup•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] User vote in blocksize through fees
Date: Sat, 13 Jun 2015 21:28:36 -0700 [thread overview]
Message-ID: <557D02F4.7090001@riseup.net> (raw)
In-Reply-To: <COL402-EAS423BB81E15B25CD20B11B10CDBA0@phx.gbl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A decentralized, distributed application should offer its users
decentralized, distributed method of weighing in on the direction of
how it evolves as well as having an open development model. The
reference to Facebook and Myspace is completely inapplicable here
because the tyranny of such spaces isn't what we have with bitcoin
(fortunately), nor would we want to try to replicate it, ever, in any
way, shape, or form.
Yes, it does bother (some) people to see the consensus based system
because of the difficulties that can be associated with implementing
it. But that's the way it is. If you don't like consensus based
systems (or decentralized, distributed systems) this is probably the
wrong space for you.
On 06/13/2015 04:57 PM, Raystonn wrote:
> Adding back the list. Did not intend to remove it. Apologies.
>
> On 13 Jun 2015 4:52 pm, Raystonn <raystonn@hotmail•com> wrote:
>
> Based on my observations, what the majority of Bitcoin users want
> is a system that can carry more transactions per second than any
> existing payment system while retaining most of the security
> offered today. The technicalities on how this is achieved are not
> as important as the end result. If the only user input is to
> technicalities, they will use that to voice their opinions.
>
> On 13 Jun 2015 4:25 pm, Danny Thorpe <danny.thorpe@gmail•com>
> wrote:
>
> I don't recall Facebook or MySpace asking end users to alter the
> parameters of their respective back-end network infrastructure.
>
> How are Bitcoin end users qualified to make an informed decision
> regarding block size limits? And why should they care?
>
> Sure, I want Bitcoin to grow its user base. But to do that,
> Bitcoin has to be accessible to the nontechnical population.
> Asking nontechnical people to make technical decisions leads
> directly to stress and confusion, which most folks find
> off-putting.
>
> And please don't call me Shirley. ;>
>
> On Sat, Jun 13, 2015 at 3:42 PM, Raystonn <raystonn@hotmail•com
> <mailto:raystonn@hotmail•com>> wrote:
>
> Surely you would prefer to actually have users? Bitcoin does not
> exist in a vacuum. Network effect alone is not enough to ensure
> success in the face of competition from alternatives with a much
> better user experience. See Facebook vs MySpace, IE vs Netscape,
> etc.
>
> On 13 Jun 2015 3:20 pm, Danny Thorpe <danny.thorpe@gmail•com
> <mailto:danny.thorpe@gmail•com>> wrote:
>
> Please forgive my ignorance, but why should Bitcoin users have a
> say in block size limits? It's the miners and Bitcoin node
> operators that bear the burden of managing large blocks, no?
>
> Users voting on network parameters sounds like neighbors voting on
> how deep my swimming pool should be.
>
> Thanks, -Danny
>
> On Fri, Jun 12, 2015 at 11:11 AM, Peter Todd <pete@petertodd•org
> <mailto:pete@petertodd•org>> wrote:
>
> Jeff Garzik recently proposed that the upper blocksize limit be
> removed entirely, with a "soft" limit being enforced via miner
> vote, recorded by hashing power.
>
> This mechanism within the protocol for users to have any influence
> over the miner vote. We can add that back by providing a way for
> transactions themselves to set a flag determining whether or not
> they can be included in a block casting a specific vote.
>
> We can simplify Garzik's vote to say that one of the nVersion bits
> either votes for the blocksize to be increased, or decreased, by
> some fixed ratio (e.g 2x or 1/2x) the next interval. Then we can
> use a nVersion bit in transactions themselves, also voting for an
> increase or decrease. Transactions may only be included in blocks
> with an indentical vote, thus providing miners with a monetary
> incentive via fees to vote according to user wishes.
>
> Of course, to cast a "don't care" vote we can either define an
> additional bit, or sign the transaction with both versions.
> Equally we can even have different versions with different fees,
> broadcast via a mechanism such as replace-by-fee.
>
>
> See also John Dillon's proposal for proof-of-stake blocksize
> voting:
>
> https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net
/msg02323.html
>
>
>
- -- 'peter'[:-1]@petertodd.org <http://petertodd.org>
> 0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778
>
> ----------------------------------------------------------------------
- --------
>
>
>
_______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> <mailto:Bitcoin-development@lists•sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
>
> ----------------------------------------------------------------------
- --------
>
>
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVfQL0AAoJEGxwq/inSG8CRqMH/0l9tHGA8figVGnIBoMgdpVi
uwMGTQTjLUf12/NFS27vT+OLMWqZRvVXvlxDF25N7la+QImhh67LqmQy8fkwGg5T
kJ6MkkFLgy05aqE/X3ywJUifOKmS3Y/RDDUJhrFjjHrsMGoF4ATtVwTpUBLik+kX
G3XRNlInmyB55UEcpyfBg9kfLz8xiy6sBPeaeGnFLCNWTs5TgJ6DTFqhBAAmE8Hw
k0tN6mW3wYS610FFkS2E3+W8O8KGs4oqAYLX/ZQOhX9oKjBvWWI4ppRpSDyBNcxd
A6VAKyU8HCuDHAEwba6gdlUa+yf4qxuZV1KCNENbvtN1CTsJ6oh0OxnEO6dtogo=
=KZmG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-06-14 4:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 23:57 Raystonn
2015-06-14 4:28 ` odinn [this message]
2015-06-14 5:46 ` Aaron Voisine
2015-06-14 21:38 ` odinn
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 18:11 Peter Todd
2015-06-12 18:20 ` Mark Friedenbach
2015-06-12 18:26 ` Matt Whitlock
2015-06-12 18:36 ` Peter Todd
2015-06-12 18:56 ` Jannes Faber
[not found] ` <CABr1YTfowMqgDZoWhDXiM0Bd3dwhVo6++FOvLntGc2HkApEbGw@mail.gmail.com>
2015-06-12 20:04 ` Eric Lombrozo
2015-06-12 23:01 ` Vincent Truong
2015-06-12 23:11 ` Luke Dashjr
2015-06-12 23:23 ` Aaron Gustafson
2015-06-12 18:22 ` Matt Whitlock
2015-06-12 18:34 ` Peter Todd
2015-06-12 18:36 ` Matt Whitlock
2015-06-12 18:39 ` Benjamin
2015-06-12 18:47 ` Peter Todd
2015-06-12 18:44 ` Peter Todd
2015-06-12 18:52 ` Matt Whitlock
2015-06-12 18:54 ` Matt Whitlock
2015-06-12 18:56 ` Aaron Gustafson
2015-06-13 22:20 ` Danny Thorpe
2015-06-13 22:24 ` Eric Lombrozo
2015-06-14 4:55 ` Chun Wang
2015-06-14 4:59 ` Jeff Garzik
2015-06-14 5:08 ` Eric Lombrozo
2015-06-14 5:13 ` Jeff Garzik
2015-06-14 5:20 ` Eric Lombrozo
2015-06-14 5:36 ` Jeff Garzik
2015-06-14 10:06 ` Mats Henricson
2015-06-14 10:34 ` Benjamin
2015-06-14 15:07 ` Jeff Garzik
2015-06-14 21:59 ` odinn
2015-06-14 20:10 ` Eric Lombrozo
2015-06-14 14:42 ` Jeff Garzik
2015-06-14 22:26 ` Mike Hearn
2015-06-15 3:59 ` Eric Lombrozo
2015-06-14 4:16 ` Stephen
2015-06-14 4:50 ` Eric Lombrozo
2015-06-14 4:56 ` Jeff Garzik
2015-06-14 7:19 ` Ashley Holman
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=557D02F4.7090001@riseup.net \
--to=odinn.cyberguerrilla@riseup$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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