public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] July 4th 2015 invalid block fork postmortem BIP number request
Date: Sat, 4 Jul 2015 06:15:06 +0000	[thread overview]
Message-ID: <CAAS2fgQx2FyEyjc0wkS4DLSPux-qCgx40XNprfzsJqVTRt4oQg@mail.gmail.com> (raw)

Unless there are objections I intend to assign myself a BIP number for
a postmortem for this event.

I've already been reaching out to parties involved in or impacted by
the fork to gather information, but I do not intend to begin drafting
for a few days (past expirence has shown that it takes time to gain
more complete understanding after an event).

If anyone is aware of services or infrastructure which were impacted
by this which I should contact to gain insight for the analysis,
please contact me off-list.

If anyone is interested in contributing to an analysis, let me know
and I'll link you to my repository when I begin drafting.  If you have
begun your own write up, please do not send it to me yet-- I'd rather
collect more data before drawing any analysis from it myself.

Thanks.


                 reply	other threads:[~2015-07-04  6:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAAS2fgQx2FyEyjc0wkS4DLSPux-qCgx40XNprfzsJqVTRt4oQg@mail.gmail.com \
    --to=gmaxwell@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    /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