public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Carsten Otto <carsten.otto@andrena.de>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
Date: Fri, 26 Jun 2015 23:07:42 +0200	[thread overview]
Message-ID: <20150626210742.GB5056@home.c-otto.de> (raw)
In-Reply-To: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

Dear all,

On Mon, Jun 22, 2015 at 02:18:19PM -0400, Gavin Andresen wrote:
> I promised to write a BIP after I'd implemented
> increase-the-maximum-block-size code, so here it is. It also lives at:
> https://github.com/gavinandresen/bips/blob/blocksize/bip-8MB.mediawiki

The URL is dead, and the BIP moved here:
https://github.com/gavinandresen/bips/blob/blocksize/bip-0101.mediawiki

Corresponding Pull Request:
https://github.com/bitcoin/bips/pull/163/

Best regards,
Dr. Carsten Otto
-- 
andrena objects ag
Büro Frankfurt
Clemensstr. 8
60487 Frankfurt

Tel: +49 (0) 69 977 860 38
Fax: +49 (0) 69 977 860 39
http://www.andrena.de

Vorstand: Hagen Buchwald, Matthias Grund, Dr. Dieter Kuhn
Aufsichtsratsvorsitzender: Rolf Hetzelberger

Sitz der Gesellschaft: Karlsruhe
Amtsgericht Mannheim, HRB 109694
USt-IdNr. DE174314824

Bitte beachten Sie auch unsere anstehenden Veranstaltungen:
http://www.andrena.de/events

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2015-06-26 21:27 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 18:18 [bitcoin-dev] Draft BIP : fixed-schedule block size increase Gavin Andresen
2015-06-22 18:33 ` Tier Nolan
2015-06-22 18:46   ` Gavin Andresen
2015-06-22 19:10 ` Martin Schwarz
2015-06-22 19:28   ` Tier Nolan
2015-06-22 19:54     ` Gavin Andresen
2015-06-22 20:12       ` Peter Todd
2015-06-22 19:23 ` Peter Todd
2015-06-23  7:35   ` Ross Nicoll
2015-08-17 15:58     ` Jorge Timón
2015-06-23 19:16   ` Peter Todd
2015-06-22 20:27 ` Kalle Rosenbaum
2015-06-22 20:46   ` Gavin Andresen
2015-06-22 20:51     ` Gavin Andresen
2015-06-22 21:52 ` Mark Friedenbach
2015-06-23 19:28 ` Peter Todd
2015-06-23 20:12   ` Gavin Andresen
2015-06-23 20:26     ` Pieter Wuille
2015-06-23 20:50       ` Peter Todd
2015-06-24  6:14         ` grarpamp
2015-06-23 20:46     ` Peter Todd
2015-06-23 21:24       ` Gavin Andresen
2015-06-26 19:08         ` Peter Todd
2015-06-26 22:01           ` Ivan Brightly
2015-06-26 19:25         ` Peter Todd
2015-06-26 22:16           ` Simon Liu
2015-06-27  2:14             ` Milly Bitcoin
2015-06-23 20:55     ` Roy Badami
2015-06-24  1:43 ` odinn
2015-06-24  3:05   ` William Madden
2015-06-24  3:49     ` Jeff Garzik
2015-06-24 13:06       ` Will
2015-06-24 13:44         ` Gavin Andresen
2015-06-25  0:32           ` Pindar Wong
2015-06-25 13:50       ` Gareth Williams
2015-06-25 14:07         ` Adam Back
2015-06-26 13:47           ` Tier Nolan
2015-06-26 15:13             ` Will
2015-06-26 17:39               ` Gavin Andresen
2015-06-26 19:07                 ` Will
2015-07-01 22:49             ` odinn
2015-08-17 13:15               ` Tier Nolan
2015-08-17 13:18                 ` Clément Elbaz
2015-08-19  3:45                 ` odinn
2015-08-17 16:11             ` Jorge Timón
2015-06-26 21:07 ` Carsten Otto [this message]
2015-06-22 19:32 Jean-Paul Kogelman
2015-06-22 20:43 ` Tier Nolan
2015-06-22 20:54 ` Peter Todd
2015-06-22 21:04   ` Stephen Morse
2015-06-22 21:32     ` Ross Nicoll
2015-08-17 15:54       ` Jorge Timón
2015-06-22 21:21   ` Gavin Andresen
2015-06-22 21:39     ` Patrick Strateman
2015-06-22 21:48     ` Tier Nolan
2015-06-23  7:59 Ross Nicoll
2015-06-24  4:31 Raystonn
2015-06-24 17:05 ` Mark Friedenbach
2015-06-24 17:24   ` Roy Badami
2015-06-24 17:23 Raystonn
2015-06-24 17:24 ` Allen Piscitello
2015-06-24 17:28 ` Roy Badami

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=20150626210742.GB5056@home.c-otto.de \
    --to=carsten.otto@andrena.de \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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