From: Devrandom <c1.bitcoin@niftybox.net>
To: Peter Todd <pete@petertodd.org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Introducing a POW through a soft-fork
Date: Mon, 06 Nov 2017 23:38:20 +0000 [thread overview]
Message-ID: <CAB0O3SXHyQhqoKtDZacWOUjzKp+3GimGABGToWrvRQgcBRE6EA@mail.gmail.com> (raw)
In-Reply-To: <CAB0O3SVsXL_zVBs-OFEaFuKTXoyYAiB8TEZStOfou7mMkHLMnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
>
> Note how you're basically proposing for the block interval to be decreased,
>> which has security implications due to increased orphan rates.
>>
>
> Note that the total transaction rate and block size don't materially
> change, so I don't
> see why the orphan rate will change. Normal blocks are constrained to have
> all of the txs of the aux blocks, so propagation time should stay the
> same. Am I missing
> something?
>
Ah, yes, I'm missing that the expected time to find each type of block is
halved, so the orphan rate doubles.
[-- Attachment #2: Type: text/html, Size: 1023 bytes --]
prev parent reply other threads:[~2017-11-06 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 5:48 [bitcoin-dev] Introducing a POW through a soft-fork Devrandom
2017-11-02 23:55 ` Tao Effect
2017-11-03 1:02 ` Devrandom
2017-11-06 19:50 ` Peter Todd
2017-11-06 20:30 ` Paul Sztorc
2017-11-06 20:55 ` Eric Voskuil
2017-11-07 4:38 ` Devrandom
2017-11-11 19:51 ` Eric Voskuil
2017-11-06 22:39 ` Devrandom
2017-11-06 23:38 ` Devrandom [this message]
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=CAB0O3SXHyQhqoKtDZacWOUjzKp+3GimGABGToWrvRQgcBRE6EA@mail.gmail.com \
--to=c1.bitcoin@niftybox.net \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=pete@petertodd.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