From: Tom Harding <tomh@thinlink.com>
To: Peter R <peter_r@gmx.com>
Cc: bitcoin-dev@lists.linuxfoundation.org,
Daniele Pinna <daniele.pinna@gmail.com>
Subject: Re: [bitcoin-dev] Unlimited Max Blocksize (reprise)
Date: Sun, 30 Aug 2015 14:10:18 -0700 [thread overview]
Message-ID: <55E3713A.5040000@thinlink.com> (raw)
In-Reply-To: <B52558A9-8897-450B-B386-503773EE0867@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
On 8/30/2015 9:54 AM, Peter R wrote:
> Like Daniele pointed out, the greedy algorithm assumed in the paper is
> asymptotically optimal in such a case.
I'm convinced.
[-- Attachment #2: Type: text/html, Size: 553 bytes --]
next prev parent reply other threads:[~2015-08-30 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 11:49 [bitcoin-dev] Unlimited Max Blocksize (reprise) Daniele Pinna
[not found] ` <B52558A9-8897-450B-B386-503773EE0867@gmx.com>
2015-08-30 21:10 ` Tom Harding [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-30 17:00 Peter R
[not found] <CAEgR2PEMueQc7GgYWYMOZgtKHvxHgoe1rT1F+YpG2x0h74+_Gw@mail.gmail.com>
[not found] ` <CAEgR2PHnJfCwMzFCrJr_TnFzRjJ7GVE-4=omva92nO6g9z2LSQ@mail.gmail.com>
2015-08-26 22:22 ` Daniele Pinna
2015-08-27 0:48 ` 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=55E3713A.5040000@thinlink.com \
--to=tomh@thinlink.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=daniele.pinna@gmail.com \
--cc=peter_r@gmx.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