From: Upal Chakraborty <bitcoin@upalc•com>
To: Hector Chu <hectorchu@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>, greg@xiph•org
Subject: Re: [bitcoin-dev] Dynamically Controlled Bitcoin Block Size Max Cap [BIP 1xx - Draft]
Date: Wed, 26 Aug 2015 17:49:29 +0530 [thread overview]
Message-ID: <CAED3CWikGkxFeVT4YYZH9oJxAPE+4kZ6rvZYuwaohqEFkbFfpg@mail.gmail.com> (raw)
In-Reply-To: <CAAO2FKHUL9wSNsSX-BgVfiPU++CjHAwYnFrgu5LGvdS8-hvaSQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Can we please keep this mail chain discussion specific to the proposed
draft -
https://github.com/UpalChakraborty/bips/blob/master/BIP-DynamicMaxBlockSize.mediawiki
?
I understand, voting process is an important subject of discussion. But,
that may be discussed in a separate mail chain.
On Wed, Aug 26, 2015 at 11:58 AM, Hector Chu via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> On 26 August 2015 at 01:29, Peter Todd via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org> wrote:
> > For instance, a very simple toy example that would work is just XORing
> your vote with SHA256(the entire blockchain)
>
> Uh, that would totally not work.
>
> I think my proposal of using CLTV to lock coins (votes) is better.
> Failing a soft-fork to implement that in time, counting votes from the
> UTXO set is also ok - the difference between that and CLTV is that it
> is not as strong an evidence of commitment.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1894 bytes --]
next prev parent reply other threads:[~2015-08-26 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:07 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
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 [this message]
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=CAED3CWikGkxFeVT4YYZH9oJxAPE+4kZ6rvZYuwaohqEFkbFfpg@mail.gmail.com \
--to=bitcoin@upalc$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=greg@xiph$(echo .)org \
--cc=hectorchu@gmail$(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