From: Simon Liu <simon@bitcartel.com>
To: Peter Todd <pete@petertodd.org>, Matt Whitlock <bip@mattwhitlock.name>
Cc: bitcoin-dev@lists.linuxfoundation.org, greg@xiph.org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft]
Date: Tue, 25 Aug 2015 14:18:16 -0700 [thread overview]
Message-ID: <55DCDB98.80004@bitcartel.com> (raw)
In-Reply-To: <20150825203744.GB3464@muck>
I don't think this would work.
If the rule is that one user can only have one vote, how do you prevent
a user running multiple nodes?
Also, how do you verify that a node is indeed a fully validating node
with its own copy of the blockchain?
On 08/25/2015 01:37 PM, Peter Todd via bitcoin-dev wrote:
>
> An interesting idea would be to design a voting mechanism such that only
> users with access to validating nodes be able to vote - a fundemental
> requirement for users to fully participate in Bitcoin's goverance.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
next prev parent reply other threads:[~2015-08-25 21:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:07 [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft] Upal Chakraborty
2015-08-25 9:19 ` Chun Wang
2015-08-25 20:16 ` Peter Todd
2015-08-25 20:26 ` Matt Whitlock
2015-08-25 20:37 ` Peter Todd
2015-08-25 21:14 ` Matt Whitlock
2015-08-25 21:28 ` Eric Voskuil
2015-08-25 21:18 ` Simon Liu [this message]
2015-08-25 21:44 ` Chun Wang
2015-08-26 0:29 ` Peter Todd
2015-08-26 6:28 ` Hector Chu
2015-08-26 12:19 ` Upal Chakraborty
2015-08-27 15:09 ` Upal Chakraborty
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=55DCDB98.80004@bitcartel.com \
--to=simon@bitcartel.com \
--cc=bip@mattwhitlock.name \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.org \
--cc=pete@petertodd.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