From: "Jorge Timón" <jtimon@jtimon•cc>
To: Erik Aronesty <erik@q32•com>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork
Date: Fri, 17 Mar 2017 11:39:07 +0100 [thread overview]
Message-ID: <CABm2gDrXrRAKzYrN9KBu+fA8r7YtnhufkP3U3ULYw3n_g-ekMA@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgLaK5SEq_2U+6o5zGe5vTduFj7Mn5ZN+zUb2RJ_CxZ=1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
Segwit allows old -> old, old -> new, new -> old and of course new -> new
txs.
On 17 Mar 2017 1:47 a.m., "Erik Aronesty via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org> wrote:
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.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists•linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 1206 bytes --]
prev parent reply other threads:[~2017-03-17 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 23:26 Erik Aronesty
2017-03-16 15:24 ` Alphonse Pace
2017-03-17 0:44 ` Erik Aronesty
2017-03-17 10:39 ` Jorge Timón [this message]
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=CABm2gDrXrRAKzYrN9KBu+fA8r7YtnhufkP3U3ULYw3n_g-ekMA@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(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