From: Andrew C <achow101@gmail•com>
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Questiosn about BIP100
Date: Thu, 27 Aug 2015 15:07:52 +0000 [thread overview]
Message-ID: <CADToNK972BgCXtZScciF_F+Db_AYWP=obXSqUS7DozY-rAmT7g@mail.gmail.com> (raw)
In-Reply-To: <CADm_WcbEhMNWKCY6CqsSTRQztTz3Ap8PMkO+csz+jptc9Nbazg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
I have been reading the pdf and one thing I can't figure out is what you
mean by "most common floor". Is that the smallest block size that has a
vote or the block size with the most votes or something else?
On Mon, Aug 24, 2015 at 10:40 AM Jeff Garzik <jgarzik@gmail•com> wrote:
> Great questions.
>
> - Currently working on technical BIP draft and implementation, hopefully
> for ScalingBitcoin.org. Only the PDF is publicly available as of today.
> - Yes, the initial deployment is in the same manner as size votes.
>
>
> On Fri, Aug 21, 2015 at 7:38 PM, Andrew C via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>> Hi all,
>>
>> Is there any client or code that currently implements BIP 100? And how
>> will it be deployed? WIll the initial fork be deployed in the same manner
>> that the max block size changes are deployed described in the bip?
>>
>> Thanks
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2232 bytes --]
next prev parent reply other threads:[~2015-08-27 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 23:38 Andrew C
2015-08-24 14:40 ` Jeff Garzik
2015-08-27 15:07 ` Andrew C [this message]
2015-08-27 20:49 ` Jeff Garzik
2015-08-28 3:02 ` jl2012
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='CADToNK972BgCXtZScciF_F+Db_AYWP=obXSqUS7DozY-rAmT7g@mail.gmail.com' \
--to=achow101@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jgarzik@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