From: Asher <asher@ashes.network>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] ashes.network
Date: Thu, 20 Aug 2015 20:12:08 -0700 [thread overview]
Message-ID: <55D69708.1000605@ashes.network> (raw)
Hi All,
I put together a draft describing an idea I had for an alternate set of
chain mechanics which solve some of the problems I see with existing
proof-of-work and proof-of-stake systems (mining centralization, wealth
concentration, nothing-at-stake, lack of full-node incentives, etc.).
I'd love to get feedback on the idea.
http://ashes.network/ashes.pdf
Thanks,
Asher
reply other threads:[~2015-08-21 3:12 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=55D69708.1000605@ashes.network \
--to=asher@ashes.network \
--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