From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
To: James MacWhyte <macwhyte@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hypothetical 2 MB hardfork to follow BIP148
Date: Tue, 30 May 2017 18:09:26 -0700 [thread overview]
Message-ID: <004E1123-8346-48B6-9BCB-94BAE00EC34B@me.com> (raw)
In-Reply-To: <CAH+Axy5yYQywpy0s9pBZt_fNoLPpWfra-cU9HrUwH71GDOchsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
That would invalidate any pre-signed transactions that are currently out there. You can't just change the rules out from under people.
> On May 30, 2017, at 4:50 PM, James MacWhyte via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>
>> The 1MB classic block size prevents quadratic hashing
>> problems from being any worse than they are today.
>>
>
> Add a transaction-size limit of, say, 10kb and the quadratic hashing problem is a non-issue. Donezo.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 1371 bytes --]
next prev parent reply other threads:[~2017-05-31 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 20:23 [bitcoin-dev] Hypothetical 2 MB hardfork to follow BIP148 Luke Dashjr
2017-05-23 23:07 ` Erik Aronesty
2017-05-30 13:27 ` Jorge Timón
2017-05-30 20:10 ` Jacob Eliosoff
2017-05-30 21:24 ` Mark Friedenbach
2017-05-30 22:26 ` Jorge Timón
2017-05-30 23:50 ` James MacWhyte
2017-05-31 1:09 ` Jean-Paul Kogelman [this message]
2017-05-31 3:07 ` Jacob Eliosoff
2017-06-02 19:40 ` Jared Lee Richardson
2017-06-12 16:27 ` Nathan Cook
2017-05-31 1:22 ` Jorge Timón
2017-05-31 4:14 ` Luke Dashjr
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=004E1123-8346-48B6-9BCB-94BAE00EC34B@me.com \
--to=jeanpaulkogelman@me.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=macwhyte@gmail.com \
/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