From: Hector Chu <hectorchu@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Voting by locking coins
Date: Sat, 8 Aug 2015 07:36:04 +0100 [thread overview]
Message-ID: <CAAO2FKG-BpYA=qSQkjVVajtQWqZgXGEFEL7N8zJj=9Xu1E6SZw@mail.gmail.com> (raw)
In-Reply-To: <CAAO2FKEFA5ujJKe8F4-5Wnp0DCYuyHWNWhdtk5O=nCZ-zGu0rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Also there may need to be weighting depending on how long the coins have
been locked for, to stop voting at the last minute having an undue
influence.
On 8 August 2015 at 07:27, Hector Chu <hectorchu@gmail•com> wrote:
> Has there ever been any discussion of locking coins till a certain date
> for casting votes on an issue?
>
> Say that the date for counting votes is 3 months from now. Every one who
> wants to cast a vote must lock coins until the vote closes (using CLTV). To
> increase the weight of your vote, lock more coins. Write your choice in the
> scriptPubKey or an OP_RETURN data output.
>
> On the date the vote closes the nodes tally up the coin values for the
> various vote options, and the choice with the highest total is the winner.
>
> Not saying this could be used to solve the block size issue necessarily,
> but we could have choices like:
> 1) Keep block size the same
> 2) Reduce block size by 10%.
> 3) Increase block size by 10%.
>
> The vote could be a rolling one. When the present vote is decided the vote
> for the next 3 months starts.
>
[-- Attachment #2: Type: text/html, Size: 1480 bytes --]
next prev parent reply other threads:[~2015-08-08 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 6:27 Hector Chu
2015-08-08 6:36 ` Hector Chu [this message]
2015-08-08 14:23 ` Peter Todd
2015-08-08 15:03 ` Hector Chu
2015-08-08 15:10 ` Peter Todd
2015-08-08 15:23 ` Hector Chu
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='CAAO2FKG-BpYA=qSQkjVVajtQWqZgXGEFEL7N8zJj=9Xu1E6SZw@mail.gmail.com' \
--to=hectorchu@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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