From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org, "Jorge Timón" <jtimon@jtimon•cc>
Subject: Re: [bitcoin-dev] Hypothetical 2 MB hardfork to follow BIP148
Date: Wed, 31 May 2017 04:14:25 +0000 [thread overview]
Message-ID: <201705310414.26724.luke@dashjr.org> (raw)
In-Reply-To: <CABm2gDoJ7S3pjdjdbKZ4-EuVXnEOj-gEPzSEvUGdtYovZaNK=g@mail.gmail.com>
On Wednesday 31 May 2017 1:22:44 AM Jorge Timón via bitcoin-dev wrote:
> Why is it
> https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L1661
> not enough at this point?
> Why the need for a transaction size limit?
Because the bottleneck is hashing the transaction, which costs (in CPU time)
based on its size. Maybe it would make sense to factor sigops into the limit,
though?
On Wednesday 31 May 2017 1:09:26 AM Jean-Paul Kogelman via bitcoin-dev wrote:
> On May 30, 2017, at 4:50 PM, James MacWhyte wrote:
> > Add a transaction-size limit of, say, 10kb and the quadratic hashing
> > problem is a non-issue. Donezo.
>
> That would invalidate any pre-signed transactions that are currently out
> there. You can't just change the rules out from under people.
Make it 100kB and I think we'd be okay. Those have always been policy-
forbidden so there should be no expectation they'd be acceptable in the
future.
While we're at it, I suggest also specifying a minimum transaction size as
well. The raw minimum possible is 60 bytes, but any sane output would need at
least a hash, so I'd say make the minimum be 8 (60 + 160-bit hash) bytes?
Luke
prev parent reply other threads:[~2017-05-31 4:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 20:23 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
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 [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=201705310414.26724.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jtimon@jtimon$(echo .)cc \
/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