From: Hector Chu <hectorchu@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Hector Chu via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Voting by locking coins
Date: Sat, 8 Aug 2015 16:03:04 +0100 [thread overview]
Message-ID: <CAAO2FKHAimcD7r1etc-Wy__1KWppYp7_pLdowO77ACDPWnF2ZQ@mail.gmail.com> (raw)
In-Reply-To: <3D142DE7-C785-46FB-A2D0-3DEF16892C64@petertodd.org>
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Thanks for this Peter. It is quite long winded and complicated so I just
wanted to clarify one particular point. In John's proposal, are the coins
actually locked up, or are they still freely spendable post-vote? Otherwise
there is no real cost to casting votes. Locking coins up is related to the
time-value of money and has a cost the longer they are locked up for.
On 8 August 2015 at 15:23, Peter Todd <pete@petertodd•org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> On 8 August 2015 02:27:35 GMT-04:00, Hector Chu via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
> >Has there ever been any discussion of locking coins till a certain date
> >for
> >casting votes on an issue?
>
> Yes, John Dillon proposed a very clever and viable blocksize vote scheme
> on this list awhile back:
> https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html
> -----BEGIN PGP SIGNATURE-----
>
> iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJVxhDI
> AAoJEMCF8hzn9Lnc47AH/Rg+JEhId23fKmUUDvYo8FA4N03nPjbsYBNdAAXHufUQ
> 6KQz8h+yjYKMBTU0r4ONyssQtqtsJtWQpLjANZlYlTB82WuPKNPhrAD3Kqkj7x+t
> L6ROTktoBnGvhPLCkRdpIjnGwcBhVFFxePQCySJrRT+w+5WZtcyVtx0JDdttJREF
> 5Ctdf2K6IbVJ10joQHY46IlGpVNiOhx4mJ2SyCHy5Ug4lWToHto0KYJplK5GDXTi
> 8IfPNrnqTjm5ExeyE3/d86je9sbHJvSYIrMsUCk74e244+VTUK35ms8xoA0n2yyn
> M1g6HAmA6OR61WvnQHaCYLT6f7XrDh8s0+BmpHrrF6E=
> =p+Go
> -----END PGP SIGNATURE-----
>
>
[-- Attachment #2: Type: text/html, Size: 2030 bytes --]
next prev parent reply other threads:[~2015-08-08 15:03 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
2015-08-08 14:23 ` Peter Todd
2015-08-08 15:03 ` Hector Chu [this message]
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=CAAO2FKHAimcD7r1etc-Wy__1KWppYp7_pLdowO77ACDPWnF2ZQ@mail.gmail.com \
--to=hectorchu@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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