From: Mirelo <mirelo@deugh-ausgam-valis.com>
To: Bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Proof-of-Loss
Date: Thu, 04 Jan 2018 05:54:31 -0500 [thread overview]
Message-ID: <d2M8re5KLKa7Q6XjnSyQycNfg6_CRu80RnzfMyw9omswk5A_wYa0ijnoamSsG1PMIjuHc6c7RQhW1aOK9zqxGO3zqmzf5kuTkANt4ImS9hY=@deugh-ausgam-valis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 160 bytes --]
Hi,
The paper now includes the pseudocode for block validation:
https://proof-of-loss.money/
Again, please direct any feedback to my email.
Regards,
Mirelo
[-- Attachment #2: Type: text/html, Size: 358 bytes --]
next reply other threads:[~2018-01-04 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 10:54 Mirelo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-04 12:39 [bitcoin-dev] Proof-of-Loss Mirelo
2017-04-05 19:12 ` Mirelo
2017-04-06 2:43 ` Erik Aronesty
2017-04-06 5:47 ` Mirelo
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='d2M8re5KLKa7Q6XjnSyQycNfg6_CRu80RnzfMyw9omswk5A_wYa0ijnoamSsG1PMIjuHc6c7RQhW1aOK9zqxGO3zqmzf5kuTkANt4ImS9hY=@deugh-ausgam-valis.com' \
--to=mirelo@deugh-ausgam-valis.com \
--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