public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Aronesty <erik@q32.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork
Date: Tue, 14 Mar 2017 19:26:17 -0400	[thread overview]
Message-ID: <CAJowKg+GGsvPAR1ywDody=GGQnEh5pwUMW48cLOmUGhU8SdDtA@mail.gmail.com> (raw)

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

Some discussion today led me to believe that a post segwit hard fork could
include:

1MB old tx non-witness segment
XMB new segwit non-witness segment
XMB witness segment

By partitioning off old transactions, it allows users of older, more
expensive validation transactions to continue using them, albeit with
higher fees required for the restricted space.

New segwit blocks, which don't have the hashing problem could be included
in the new non-witness segment of the block.

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

             reply	other threads:[~2017-03-14 23:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 23:26 Erik Aronesty [this message]
2017-03-16 15:24 ` [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork Alphonse Pace
2017-03-17  0:44   ` Erik Aronesty
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='CAJowKg+GGsvPAR1ywDody=GGQnEh5pwUMW48cLOmUGhU8SdDtA@mail.gmail.com' \
    --to=erik@q32.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