📅 Original date posted:2015-08-08 📝 Original message:Also there may need to be ...

Hector Chu [ARCHIVE] /

npub170s…r45x

2023-06-07 15:46:25

in reply to nevent1q…xhhp

📅 Original date posted:2015-08-08
📝 Original message: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 at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150808/19a90ba4/attachment.html>;

Author Public Key

npub170s9de2ganthnna75443h70tnsn2lvmcq5365r0juk8nfa93lthqwjr45x

Show more details

Published at

2023-06-07 15:46:25

Kind type

1 Short Text Note

Event JSON

{ "id": "6e291410bf4df8ed28bdf93d53ac46610af88771c75ee391f7f2696c7778cbed", "pubkey": "f3e056e548ecd779cfbea56b1bf9eb9c26afb3780523aa0df2e58f34f4b1faee", "created_at": 1686152785, "kind": 1, "tags": [ [ "e", "d753a84f254beae574a9326c0d242f73489f56d83af0bdc6dd6d488c486aa8d4", "", "root" ], [ "e", "8f7ff8073375a49d8818d16e37c39e35ff9172d3da257b2c68a20f08a42f5da6", "", "reply" ], [ "p", "f3e056e548ecd779cfbea56b1bf9eb9c26afb3780523aa0df2e58f34f4b1faee" ] ], "content": "📅 Original date posted:2015-08-08\n📝 Original message:Also there may need to be weighting depending on how long the coins have\nbeen locked for, to stop voting at the last minute having an undue\ninfluence.\n\nOn 8 August 2015 at 07:27, Hector Chu \u003chectorchu at gmail.com\u003e wrote:\n\n\u003e Has there ever been any discussion of locking coins till a certain date\n\u003e for casting votes on an issue?\n\u003e\n\u003e Say that the date for counting votes is 3 months from now. Every one who\n\u003e wants to cast a vote must lock coins until the vote closes (using CLTV). To\n\u003e increase the weight of your vote, lock more coins. Write your choice in the\n\u003e scriptPubKey or an OP_RETURN data output.\n\u003e\n\u003e On the date the vote closes the nodes tally up the coin values for the\n\u003e various vote options, and the choice with the highest total is the winner.\n\u003e\n\u003e Not saying this could be used to solve the block size issue necessarily,\n\u003e but we could have choices like:\n\u003e 1) Keep block size the same\n\u003e 2) Reduce block size by 10%.\n\u003e 3) Increase block size by 10%.\n\u003e\n\u003e The vote could be a rolling one. When the present vote is decided the vote\n\u003e for the next 3 months starts.\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150808/19a90ba4/attachment.html\u003e", "sig": "a7ee2f38d99afb6e9f4fafd6a1513c0d8b6d81e4b6f20435c4b2901da960d741f96d079d82df00bea61f4950e1ed3a2751384fd8ab541c15b1457cc7c878626c" }