From: Nick Simpson <nick@mynicknet•com>
To: Stephen Reed <stephenreed@yahoo•com>,
Stephen Reed <stephenreed@yahoo•com>,
"bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Cooperative Proof-of-Stake whitpaper
Date: Tue, 20 May 2014 11:42:40 -0500 [thread overview]
Message-ID: <f0c1b2dc-963a-4ea2-82c0-31b0d339d46c@email.android.com> (raw)
In-Reply-To: <1400602373.46778.YahooMailNeo@web160501.mail.bf1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
Referring to the subsidy for miners as "wasting it on miners" isn't going to garner you much favor.
On May 20, 2014 11:12:53 AM CDT, Stephen Reed <stephenreed@yahoo•com> wrote:
>I completed a whitepaper for Bitcoin a proof-of-stake version which
>uses a single nomadic verifiable mint agent and distributed replication
>of a single blockchain by compensated full nodes to achieve 6-hop,
>sub-second transaction acknowledgement times. Plus it pays dividends to
>holders instead of wasting it on miners. Subsidized transaction fees
>are thus lower.
>
>https://docs.google.com/document/d/1C4m-MFnxw0JjDorzrKs_IRQRqD9ila79o0IDt6KsbcE
>
>
>Because the code is not yet written, this idea is half-baked so to
>speak. Comments appreciated on my project thread, which will be a
>development diary. I plan a hard fork of the Bitcoin blockchain in
>early 2016, after a year of public system testing, and conditioned on
>wide approval.
>
>https://bitcointalk.org/index.php?topic=584719.msg6397403#msg6397403
>
>-Steve
>
>Stephen L. Reed
>Austin, Texas, USA
>512.791.7860
>
>------------------------------------------------------------------------
>
>------------------------------------------------------------------------------
>"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>Instantly run your Selenium tests across 300+ browser/OS combos.
>Get unparalleled scalability from the best Selenium testing platform
>available
>Simple to use. Nothing to install. Get started now for free."
>http://p.sf.net/sfu/SauceLabs
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Bitcoin-development mailing list
>Bitcoin-development@lists•sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 3108 bytes --]
next prev parent reply other threads:[~2014-05-20 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 16:12 Stephen Reed
2014-05-20 16:42 ` Nick Simpson [this message]
2014-05-21 15:52 ` Benjamin Cordes
2014-05-21 6:47 ` Odinn Cyberguerrilla
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=f0c1b2dc-963a-4ea2-82c0-31b0d339d46c@email.android.com \
--to=nick@mynicknet$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=stephenreed@yahoo$(echo .)com \
/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