From: "t. khan" <teekhan42@gmail•com>
To: Tom Zander <tomz@freedommail•ch>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - 'Block75' - New algorithm
Date: Mon, 2 Jan 2017 16:05:58 -0500 [thread overview]
Message-ID: <CAGCNRJpBMEha+cqXbgL6z9Fk5aoDOJF8tHu+XhYmMtgmdY2osw@mail.gmail.com> (raw)
In-Reply-To: <1944321.hguq3JoYe1@cherry>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Mon, Jan 2, 2017 at 3:35 PM, Tom Zander <tomz@freedommail•ch> wrote:
> If the input of your math is completely free and human created, how does it
> follow that it was math that created it ?
> Why do you want it math created anyway?
The beauty of math is that everyone on the planet agrees how it works.
Everything in Bitcoin is math, with the exception of the blocksize limit
(1MB) which was a stop-gap solution at the time.
> A maximum is needed, yes. But does it have to be part of the protocol?
> A simple policy which is set by node operators (reject block if greater
> than
> X bytes) will solve this just fine, no?
No. That would be an epic disaster. There's no such thing as a "simple
policy" when humans are involved. Obviously no one would agree on what X
bytes would be and you'd have some nodes rejecting blocks that others
already accepted.
- t.k.
[-- Attachment #2: Type: text/html, Size: 1373 bytes --]
next prev parent reply other threads:[~2017-01-02 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:04 t. khan
2017-01-02 19:01 ` Tom Zander
2017-01-02 19:32 ` t. khan
2017-01-02 20:35 ` Tom Zander
2017-01-02 21:05 ` t. khan [this message]
2017-01-02 22:33 ` Tom Zander
2017-01-02 21:19 ` Luke Dashjr
2017-01-02 22:01 ` Tom Zander
2017-01-03 14:28 ` t. khan
2017-02-13 11:21 ` Hampus Sjöberg
2017-01-02 20:04 ` Luke Dashjr
2017-01-02 20:41 ` t. khan
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=CAGCNRJpBMEha+cqXbgL6z9Fk5aoDOJF8tHu+XhYmMtgmdY2osw@mail.gmail.com \
--to=teekhan42@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=tomz@freedommail$(echo .)ch \
/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