Distributed Systems

01 Mar 2016

Perspectives on Blockchains and Cryptocurrencies

in Blockchain, Ceptr, Crypto, Currencies, Distributed Systems
blockchain-visualizationsMany are looking to the blockchain to solve many decentralization and consensus problems. I believe the infrastructure people are seeking is possible to build, but not in the way blockchain and cryptocurrencies have been approaching it so far.  There are fundamental flaws to the current popular approach that will keep it from ever reaching the scale on which we need collective intelligence, currencies, sense-making and distributed computing infrastructure to operate. 
 
Of course, this is why we've been building Ceptr – to provide the necessary infrastructure for these kinds of distributed systems. It solves all the same problems, but has been built from fundamentally different initial assumptions, so the more you know about cryptocurrencies, the harder it can be to understand why we're doing what we're doing.
 
I'll start with a summary of highlights and then drill into greater detail in the next posts - providing some examples of ways to make these kinds of distributed applications and cryptocurrencies work on a large scale.
 
Cl says to H: How do I know you’re not double-spending that electron?
31 Jan 2016

The Sovereign Accountable Commons

in Commons, Commonwealth, Currencies, Distributed Systems, Mutual Sovereignty, Reputation, Sovereingty

[This is an abstract outlining some stuff we need to write up about the Sovereign Accountable Commons as a pattern enabled by Ceptr. I wrote this up to submit to for a book about Decentralizing the Commons via the P2P Foundation site.]

The Sovereign Accountable Commons (SAC) is akin to Decentralized Autonomous Organizations on the blockchain but they leverage a different distributed architecture, Ceptr. Ceptr is a new technology platform for building Distributed Apps and for enhancing collective intelligence in the process of being released by the MetaCurrency project in early 2016.

Sovereign:

An SAC runs as a collectively distributed application. As long as at least one person wants to run it, it can't be shut down. Two or nodes running it make it a collective. It's algorithms set availability and redundancy based on size and scale of the network.

Everybody in a group is an equal peer, subject to the same rules, processes, and procedures, because everybody is running a copy of the same instruction set. This “code as law” applies to holding of assets, management of assets, interactions, transactions, governance, releasing new versions of “code as law,” and every aspect of ongoing operation of the SAC.