From: Alphonse Pace <alp.bitcoin@gmail•com>
To: Erik Aronesty <erik@q32•com>,
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 10:24:14 -0500 [thread overview]
Message-ID: <CAMBsKS87Cu+NtWTuOgeA7hmgTpW9Et-uHdpYkofNV0a73fM+8g@mail.gmail.com> (raw)
In-Reply-To: <CAJowKg+GGsvPAR1ywDody=GGQnEh5pwUMW48cLOmUGhU8SdDtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
This unnecessarily complicates transaction selection for miners by
introducing a second (and possibly third if I understand your proposal
correctly) dimension to try to optimize.
See: https://en.wikipedia.org/wiki/Bin_packing_problem
Segwit already solves this exact issue by replacing block size with block
weight, so I fail to see how this proposal would make any improvements
without introducing significant complications.
[-- Attachment #2: Type: text/html, Size: 627 bytes --]
next prev parent reply other threads:[~2017-03-16 15:24 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 [this message]
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=CAMBsKS87Cu+NtWTuOgeA7hmgTpW9Et-uHdpYkofNV0a73fM+8g@mail.gmail.com \
--to=alp.bitcoin@gmail$(echo .)com \
--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