public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Aronesty <erik@q32.com>
To: Alphonse Pace <alp.bitcoin@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork
Date: Thu, 16 Mar 2017 20:44:27 -0400	[thread overview]
Message-ID: <CAJowKgLaK5SEq_2U+6o5zGe5vTduFj7Mn5ZN+zUb2RJ_CxZ=1A@mail.gmail.com> (raw)
In-Reply-To: <CAMBsKS87Cu+NtWTuOgeA7hmgTpW9Et-uHdpYkofNV0a73fM+8g@mail.gmail.com>

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

Yeah, it does make things harder, and it's easy enough to soft fork to
handle arbitrary opt-in protocol improvements, new much larger block sizes,
whatever you want.   Even OK to migrate to a new system by not allowing
old->old or new->old transactions.

[-- Attachment #2: Type: text/html, Size: 305 bytes --]

  reply	other threads:[~2017-03-17  0:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 23:26 [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork Erik Aronesty
2017-03-16 15:24 ` Alphonse Pace
2017-03-17  0:44   ` Erik Aronesty [this message]
2017-03-17 10:39     ` Jorge Timón

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='CAJowKgLaK5SEq_2U+6o5zGe5vTduFj7Mn5ZN+zUb2RJ_CxZ=1A@mail.gmail.com' \
    --to=erik@q32.com \
    --cc=alp.bitcoin@gmail.com \
    --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