From: Stephen Morse <stephencalebmorse@gmail•com>
To: Vincent Truong <vincent.truong@procabiak•com>
Cc: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Max Block Size: Simple Voting Procedure
Date: Tue, 2 Jun 2015 23:36:00 -0400 [thread overview]
Message-ID: <CABHVRKQbTa5SA=CpGK2+Fpqxo7V3VCRKVigMrEJ_PvUg5owPiQ@mail.gmail.com> (raw)
In-Reply-To: <CACrzPe=vNd8T0B4DGH3dTE9S9S1jEU9k6_5Uz_NUP1ZEgC8uYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Vincent,
> Some changes:
>
> Votes need to be 100%, not 50.01%. That way small miners have a fair
> chance. A 50.01% vote means large miners call the shots.
>
While I like the idea of possibly requiring more than 50%, you wouldn't
want to have a situation where a minority of uncooperative (or just lazy)
miners don't add their votes and hold up progress. Maybe 2/3 instead of
1/2, though.
> Users (people who make transactions) need to vote. A vote by a miner
> shouldn't count without user votes. Fee incentives should attract
> legitimate votes from miners. A cheating miner will be defeated by another
> miner who includes those votes, and take the fees.
>
> This lets wallet providers and exchanges cast votes (few wallets will
> implement prompts and will just auto vote, so if you don't agree, switch
> wallets. Vote with your wallet).
>
The idea of voting with your wallet, while appealing, is technically
infeasible. Miners can fill their blocks with any type of transactions,
including their own specially designed transactions. And any fees from
these transactions can be collected right back into their coinbase
transaction.
- Stephen
[-- Attachment #2: Type: text/html, Size: 1708 bytes --]
next prev parent reply other threads:[~2015-06-03 3:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 19:04 Stephen Morse
2015-06-02 21:26 ` Matt Whitlock
2015-06-03 0:30 ` Stephen Morse
[not found] ` <CAM7BtUod0hyteqx-yj8XMwATYp73Shi0pvdcTrW0buseLGc_ZQ@mail.gmail.com>
[not found] ` <CABHVRKT7H1p67Bz_T_caaGFnfuswnC+kXKGdkpRhtXUZQv3HtQ@mail.gmail.com>
[not found] ` <CAM7BtUrN9D__ha63Qfs2Fi4HSUFWb8BArHni9yFKRSdLSxCNnA@mail.gmail.com>
2015-06-03 2:33 ` Stephen Morse
2015-06-03 3:08 ` Vincent Truong
2015-06-03 3:36 ` Stephen Morse [this message]
2015-06-03 4:18 ` Pindar Wong
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='CABHVRKQbTa5SA=CpGK2+Fpqxo7V3VCRKVigMrEJ_PvUg5owPiQ@mail.gmail.com' \
--to=stephencalebmorse@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=vincent.truong@procabiak$(echo .)com \
/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