From: Mirelo <mirelo@deugh-ausgam-valis•com>
To: Bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Proof-of-Loss -- Errata
Date: Tue, 07 Feb 2017 20:34:29 -0500 [thread overview]
Message-ID: <SxMWjK2t9ewJnV8EYSUY9hIccG_MDsVduGIFHbabUmIcv__L46iNj42pWntzyLiknSr8-IZlHZAFI6ynX2zU8TwyhPBPRIs5o5Wi5vGuwUA=@deugh-ausgam-valis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
There was an error on page 5 of the paper, which made the block-chaining odds formula confusing. The error was in the text, not in the formula, and consisted of assuming the affected route as always being the rewarded one, which is false. The corrected version is already available at the same URL ([https://proof-of-loss.money](https://proof-of-loss.money/)). The new file's date is 02/07/2017, and downloading it will probably require clearing the browser's cache.
I would greatly appreciate any feedback, preferably directly to my email, to avoid overloading this list with something not directly related to Bitcoin.
Mirelo
[-- Attachment #2: Type: text/html, Size: 3287 bytes --]
reply other threads:[~2017-02-08 1:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='SxMWjK2t9ewJnV8EYSUY9hIccG_MDsVduGIFHbabUmIcv__L46iNj42pWntzyLiknSr8-IZlHZAFI6ynX2zU8TwyhPBPRIs5o5Wi5vGuwUA=@deugh-ausgam-valis.com' \
--to=mirelo@deugh-ausgam-valis$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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