From: Dave Scotese <dscotese@litmocracy•com>
To: Jeff Garzik <jgarzik@gmail•com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 100 specification
Date: Wed, 2 Sep 2015 21:45:38 -0700 [thread overview]
Message-ID: <CAGLBAhdcuWNVzw4AOoe+2m7-TJEi=dXBL702rbrp28E3V9bLvQ@mail.gmail.com> (raw)
In-Reply-To: <CADm_WcZyK6LUcuKqSEuR-q0hTZOC3EdJsqY1HrS_ow0knDY=7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I suggest revising these items for clarity (and I'm guessing on the first
one)
Calculate hardLimit by examining the coinbase scriptSig votes of the
previous 12,000 blocks, and taking the 20th percentile.
A new hardLimit may not increase or decrease by more than 1.2x beyond
the prior hardLimit.
to:
The new hardLimit is calculated by sorting the coinbase scriptSig votes
of the last 12,000 blocks from lowest to highest and using the vote of the
2400th block.
If the vote of the 2400th block is a change of less than 20%, use it as
the new hardLimit. Otherwise, change the hardLimit to be closer to that
vote, to either 120% or 80% of the current hardLimit.
I don't understand #5, 75% rule. Shouldn't invalid version 4 blocks always
be rejected?
notplato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJV58/5AAoJEL8dSijmIbHt16IH/0jAr3v1HjWW7N1awNxeAABs
GIvOFYuZAcPkZvWZQc4JRAppglqeBfYqWl2gpyywSBK1SXjsY8zdo3t7xAK/IJfB
05hnv1GGutG3dLTzJBEXaPx62SLukepC1pzEH7rlwWvVuE9zcRqVE1eGbBEUjA9c
sGPr0z9BNeLoTbllyl3Jndz9N2Vnd6bBTxRgBlfkm/Y5ovc+GhyKZyX3Pdmj5Pga
E6foOsvqNXQJqPl8WCODsnfPSshyb7YRNFrBB9A+tpjvj4UMc8PxOpL6IX/nJpOt
jlfRoKVw2YBEodvda+9P6S54GlGFazyHhwJ11F5YCNnWW1bKoQrqJU6ofgmyxMM=
=QWra
-----END PGP SIGNATURE-----
On Wed, Sep 2, 2015 at 8:33 PM, Jeff Garzik via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> BIP 100 initial public draft:
> https://github.com/jgarzik/bip100/blob/master/bip-0100.mediawiki
>
> Emphasis on "initial" This is a starting point for the usual open source
> feedback/iteration cycle, not an endpoint that Must Be This Way.
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto
[-- Attachment #2: Type: text/html, Size: 3289 bytes --]
next prev parent reply other threads:[~2015-09-03 4:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 3:33 Jeff Garzik
2015-09-03 4:45 ` Dave Scotese [this message]
2015-09-03 7:57 ` jl2012
2015-09-03 11:20 ` Btc Drak
2015-09-03 14:34 ` Jeff Garzik
2015-09-03 15:58 ` Btc Drak
2015-09-03 16:13 ` Jorge Timón
2015-09-03 11:59 ` Tier Nolan
2015-09-03 16:32 ` jl2012
2015-09-03 16:35 ` Jeff Garzik
2015-09-03 17:32 ` Btc Drak
2015-09-03 17:52 ` Peter Todd
2015-09-04 7:53 ` Andy Chase
2015-09-04 15:37 ` Simon Liu
2015-09-04 15:40 ` Btc Drak
2015-09-03 14:35 ` Jeff Garzik
2015-09-03 19:40 ` Simon Liu
2015-09-03 20:15 ` Oliver Petruzel
2015-09-03 20:34 ` Dave Scotese
2015-09-04 3:50 ` Peter Todd
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='CAGLBAhdcuWNVzw4AOoe+2m7-TJEi=dXBL702rbrp28E3V9bLvQ@mail.gmail.com' \
--to=dscotese@litmocracy$(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