From: "Jorge Timón" <jtimon@jtimon.cc>
To: Marcel Jamin <marcel@jamin.net>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Yet another blocklimit proposal / compromise
Date: Fri, 11 Sep 2015 18:22:26 +0200 [thread overview]
Message-ID: <CABm2gDqArkYxJmQfPKTjPjRQUHXjEjHb+8UUe54RNr6sHiUhKA@mail.gmail.com> (raw)
In-Reply-To: <CAAUq486GxLw25TW2SV6d8vCCdhY5SEjfdAPCOhV6ta+hoyJY5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
Unfortunately the relation between block maximum size and mining
centralization is much more complex than that.
On Sep 9, 2015 3:00 PM, "Marcel Jamin" <marcel@jamin.net> wrote:
> I think the overlap of people who want to run a serious mining operation
> and people who are unable to afford a slightly above average internet
> connection is infinitesimally small.
>
> 2015-09-09 20:51 GMT+02:00 Jorge Timón <jtimon@jtimon.cc>:
>
>>
>> On Sep 9, 2015 8:36 PM, "Marcel Jamin via bitcoin-dev" <
>> bitcoin-dev@lists.linuxfoundation.org> wrote:
>> >
>> > I propose to:
>> >
>> > a) assess what blocklimit is currently technically possible without
>> driving up costs of running a node up too much. Most systems currently
>> running a fullnode probably have some capacity left.
>>
>> What about the risk of further increasing mining centralization?
>>
>
>
[-- Attachment #2: Type: text/html, Size: 1571 bytes --]
next prev parent reply other threads:[~2015-09-11 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 7:55 [bitcoin-dev] Yet another blocklimit proposal / compromise Marcel Jamin
2015-09-09 18:51 ` Jorge Timón
2015-09-09 19:00 ` Marcel Jamin
2015-09-11 16:22 ` Jorge Timón [this message]
2015-09-11 16:47 ` Adam Back
2015-09-11 17:54 ` Marcel Jamin
2015-09-11 18:17 ` 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=CABm2gDqArkYxJmQfPKTjPjRQUHXjEjHb+8UUe54RNr6sHiUhKA@mail.gmail.com \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=marcel@jamin.net \
/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