From: xor <xor@freenetproject.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Humans constantly arguing about bsize proves that computers should decide
Date: Sun, 16 Aug 2015 11:46:06 +0200 [thread overview]
Message-ID: <1527744.9EQbJdl4Dy@1337h4x0r> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hey folks,
so you've been stressed with arguing about what to do with the block size for
months now :(
Why not realize that the unfruitful permanent need for administrators to tweak
a magical, god-given (= Satoshi-given) constant is a *strong* indicator for
something which should be delegated to a self-adjusting system instead?
new_max_blocksize = some_averaging_function(previous_block_sizes);
end_of_flamewar();
continue_with_REAL_development();
Systems which do not require any human intervention are always more beautiful,
and especially when trying to design a decentralized P2P network :)
Greetings,
xor, a developer working for the Freenet anonymous P2P network
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2015-08-16 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 9:46 xor [this message]
2015-08-16 10:13 ` [bitcoin-dev] Humans constantly arguing about bsize proves that computers should decide Andrew
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=1527744.9EQbJdl4Dy@1337h4x0r \
--to=xor@freenetproject.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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