From: Stephen Reed <stephenreed@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] New paper: Research Perspectives and Challenges for Bitcoin and Cryptocurrencies
Date: Thu, 5 Mar 2015 00:06:15 -0500 [thread overview]
Message-ID: <74B059E0-294D-4F8F-BC62-C91157A385D1@yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
You might consider the dimension taken by the cooperative mining approach of AI Coin, an altcoin that will launch April 27. The coin is an embodiment of principles described in my whitepaper last May, "Bitcoin Cooperative Proof of Stake".
http://arxiv.org/abs/1405.5741
Currently we do not use staking, as network-wide algorithmic trustworthiness provides the security directly. Network operations, although highly automated with intelligent software agents, has a human-in-the-loop for oversight.
Our innovation enables immediate settlement of transactions. Peers in our network cooperate, taking turns creating new blocks. There is single version of the blockchain which is appended to by a single peer, and is replicated by the other peers. Our peers wrap Bitcoind instances, controlling transaction and new block routing to form a scalable super peer topology. Peers have self-signed X.509 certificates which encrypt messages and prevent impersonation. The tamper-evident technology that secures Bitcoin's blockchain and transactions is extended to secure the entire network. Inspired by an idea published by Nick Szabo, our peers maintain tamper-evident logs which are replayed, verified and signed by other peers. Aside from the whitepaper, more current technical information can be found on our forum - where I would be glad to answer questions and debate skeptics - instead of responding in this list off topic.
http://ai-cointalk.org
I would like thank those here and on IRC who last year encouraged me think outside the box.
-Steve
CTO AI Coin, Inc.
512.791.7960
http://ai-coin.org
[-- Attachment #2: Type: text/html, Size: 2106 bytes --]
next reply other threads:[~2015-03-05 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 5:06 Stephen Reed [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 16:48 Andrew Miller
2015-03-03 1:57 ` Ricardo Filipe
2015-03-04 12:19 ` Tim Ruffing
2015-03-04 15:28 ` Mike Hearn
2015-03-08 12:23 ` Pindar Wong
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=74B059E0-294D-4F8F-BC62-C91157A385D1@yahoo.com \
--to=stephenreed@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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