Private and confidential. Images and text (where applicable) copyright Eris Industries Limited, 2015.
What’s wrong with crypto
IT’S JUST SOFTWARE.
Idealism, pragmatism, and “blockchain 2.0”
Private	
  and	
  Confiden.al 2
Before we begin
Private	
  and	
  Confiden.al 3
Most people look at blockchains like this
Private	
  and	
  Confiden.al 4
We look at blockchains like this
Private	
  and	
  Confiden.al 5
Our theory: mathematical infrastructure will
replace physical infrastructure
Current platform architecture requires that each market participant
runs all of their own standalone human and machine infrastructure.
This is a nightmare, and extremely expensive, to scale.
BUT
What if we could run shared data infrastructure without the multiple-
redundant, hierarchical, centralised points of failure?
Private	
  and	
  Confiden.al 6
Our theory: blockchains
Blockchains are distributed databases that house protocols for
distributed data management
Blockchains allow for high verifiability, systemic resiliency, ease of use,
and low operating costs out of the box
Private	
  and	
  Confiden.al 7
Our theory: smart contracts
Smart contracts are complex coded instructions which almost any
blockchain is able to run and execute
Blockchains aren’t magical internet money machines -
they’re just software and will do exactly what we tell them to do
What Bitcoin does for clearing and settlement, smart contracts can do
for virtually any other business process
Private	
  and	
  Confiden.al 8
Addressing some common misconceptions
“Mining”
“Decentralisation”
“Network effects”
Private	
  and	
  Confiden.al 9
MINING
Is not required to validate transactions
Is not (always) required to secure the chain
(depends on chaintype in question & system
design)
- - -
Is one of many possible security strategies
Is designed to incentivise nodes to propose
valid blocks when no-one is in charge
Private	
  and	
  Confiden.al 10
DECENTRALISATION
Reverses cause and effect
Does not work within existing legal paradigms
Causes more commercial problems than it solves
Private	
  and	
  Confiden.al 11
NETWORK EFFECT
I’ll get to that in a bit.
Private	
  and	
  Confiden.al 12
What we do
Eris makes smart contracts easy to use.
You can use a blockchain and explore smart contracts’ potential in your
organisation
Without needing to use a cryptocurrency
Without paying anything to anyone
Without being restricted to any one innovation
Private	
  and	
  Confiden.al 13
DEFINITIONS:
WHAT IS A BLOCKCHAIN?
Private	
  and	
  Confiden.al 14
How the internet currently works
Private	
  and	
  Confiden.al 15
On somebody else’s (central) server
Private	
  and	
  Confiden.al 16
Blockchains: no servers, simple hardware
Private	
  and	
  Confiden.al 17
REDEFINING THE BLOCKCHAIN:
JUST ANOTHER DISTRIBUTED DATABASE
1) distributed rulebooks
2) that track changes made to them
3) where write permissions are
controlled by public-private key
cryptography
and
4) as a result, we can be fairly certain
that something which is on a
blockchain belongs there.
(Sort of like French law
actually)
Private	
  and	
  Confiden.al 18
Blockchains give us verifiable data.
1) Signature rules - tell ‘em what you’re gonna say
Let’s agree on our ability to write to the data set.
2) Network rules - say it
Let’s agree how we communicate with each other.
3) History rules - tell ‘em what you said
Let’s agree on what the world-state of our data is and was, with
the ability to easily check whether tampering has occurred.
Private	
  and	
  Confiden.al 19
RULE 1: TELL ‘EM WHAT YOU’RE GONNA SAY
Effectively: users’ rules of the game;
pre-defined access permissions
Who can broadcast transactions?
What actions can a user perform?
How do they go about “spending” it?
Can I reference data “offchain?”
Private	
  and	
  Confiden.al 20
RULE 2: SAY IT
Open standard for common
communication to achieve a common
goal
What can we say?
What do words mean?
Who do we listen to?
Private	
  and	
  Confiden.al 21
RULE 3: TELL ‘EM WHAT YOU SAID
Also known as the “consensus
protocol”
Agreeing the truth
What has been said?
Who has said it?
Is the record correct?
“The dragon that eats its own tail:”
what has happened (past) determines
what can happen (now and future)
Private	
  and	
  Confiden.al 22
PUT IT ALL TOGETHER
="
Mais,!c’est!en!français…"
Private	
  and	
  Confiden.al 23
TRANSLATE IT INTO ENGLISH
Private	
  and	
  Confiden.al 24
Hey, presto.
That’s a blockchain application.
Private	
  and	
  Confiden.al 25
What Bitcoin demonstrated about the
blockchain (as compared to other distributed
database types)
Security
Verifiability
Resiliency
SIMPLICITY & EASE OF USE
Private	
  and	
  Confiden.al 26
Permissioning simply makes these qualities
commercially viable.
Accountability.
Controllability.
Repeatability.
Reversibility.
Private	
  and	
  Confiden.al 27
Permissioning means that blockchain solutions can be
engineered…
to do exactly what you want them to do
Private	
  and	
  Confiden.al 28
DEFINITIONS:
WHAT IS A SMART CONTRACT?
Private	
  and	
  Confiden.al 29
Nick Szabo, 1994
Quote courtesy of Tim Swanson’s presentation entitled “Defining Smart Contracts.”
Private	
  and	
  Confiden.al 30
Richard Gendal Brown, 2015
Quote courtesy of Tim Swanson’s presentation entitled “Defining Smart Contracts.”
Private	
  and	
  Confiden.al 31
Casey Kuhlman, 2015
“A smart contract is a script which allows for the
cryptographically verifiable execution of code over
cryptographically verifiable data.”
Private	
  and	
  Confiden.al 32
Why this definition makes sense
Blockchains aren’t ledgers, they’re data stores
Blockchains = verifiable data (state)
Smart contracts = verifiable execution of code (write)
HP: “The contract is the transaction”
“The marmot is the contract”
Private	
  and	
  Confiden.al 33
What do all these definitions have in common?
Characteristics:
Scripts with state
Almost any blockchain capable of running them
Benefits:
Can describe more complex data driven-processes
Signature schemes apply to arbitrary data
Limitations:
Do not “self-enforce” (or “self-execute”)
Work best when value is extrinsic to the data structure
Private	
  and	
  Confiden.al 34
HOW DO I USE SMART CONTRACTS?
Private	
  and	
  Confiden.al 35
Example: distributed Reddit (June 2014)
Private	
  and	
  Confiden.al 36
Example: People’s Republic of DOUG (June 2014)
Private	
  and	
  Confiden.al 37
Example: distributed YouTube (March 2015)
Private	
  and	
  Confiden.al 38
Examples: live pilots with MFIs
Watch this space.
Private	
  and	
  Confiden.al 39
WHO’S INTERESTED?
Private	
  and	
  Confiden.al 40
Basically everyone
Private	
  and	
  Confiden.al 41
Integrators, developers, consultants, think tanks
With the exception of marmcorp.com, no actual marmots are building with the Eris platform presently.
Private	
  and	
  Confiden.al 42
Other startups using similar technology
Private	
  and	
  Confiden.al 43
NETWORK EFFECT
(I was saving this for later, remember?)
Market ≠ Network
Like running the Facebook playbook for Enterprise
Linux.
Private	
  and	
  Confiden.al 44
HOW SHOULD WE CHANGE OUR THINKING?
Private	
  and	
  Confiden.al 45
To begin with
Blockchains are not a scarce resource
Private	
  and	
  Confiden.al 46
Consequences
Dramatic expansion in feasible, application-specific
blockchain use-cases
Shift of emphasis away from money, payments and
“assets”, and towards process automation and data
management
Private	
  and	
  Confiden.al 47
Cryptocurrency is only one application of blockchain technology.
CRYPTOCURRENCY RULE 1
Open to all
Evades government controls
CRYPTOCURRENCY RULE 2
Distributed architecture = resilient to interference/
destruction
CRYPTOCURRENCY RULE 3
Relies on competitive “mining” and awards “Bitcoins” etc
Process is automatic, no central third party required
Fraud difficult (but not impossible)
Private	
  and	
  Confiden.al 48
Getting away from the protocol and into the
application: a how-to guide.
MyChain Rule 1:
Must be controllable in every respect
All write permissions must be accessible through P/P key crypto
In 99.99% of cases in finance, cannot be open/fully public
Can talk to my other databases
MyChain Rule 2:
Cryptocurrency got this mostly right
MyChain Rule 3:
Change any aspect of the system on command
Commercial standards of data security/certainty needed
Private	
  and	
  Confiden.al 49
HOW TO AVOID “PUT IT ON A BLOCKCHAIN”
SYNDROME
Private	
  and	
  Confiden.al 50
STEP 1:
DEFINE THE PROBLEM
Does a blockchain solve a problem I
have?
YES:
Coordinating actions of independent actors
Simplifying multiple processes into single process
Timely verification is paramount (e.g. settlement)
Reducing supervision and oversight cost
Need to scale without (much) hardware
Private	
  and	
  Confiden.al 51
DOES THIS SOLVE A PROBLEM I HAVE?
NO:
Requires speed (blockchains are comparatively slow)
Requires heavy computation (blockchains are passive)
Is fully automatic anyway (order of magnitude improvement
harder to achieve; though blockchains could still be useful qua
secure open standard)
Private	
  and	
  Confiden.al 52
STEP 2:
DESIGN YOUR APPLICATION
Source: “Solidity, Part 1: an Introduction to Smart Systems of Smart Contracts.” https://eng.erisindustries.com/tutorials/2015/03/11/solidity-1/
STEP 3:
BUILD
STEP 4:
ITERATE
Because the circumstances change
Because business changes
Because you’ll screw up
Because you’ll improve
Private	
  and	
  Confiden.al 55
TO RECAP:
Public blockchains = neat
Permissioned blockchains = neat for commerce
Smart contracts FTW in either case
Eris helps you manage your smart contract
applications, no matter the chain
Private	
  and	
  Confiden.al 56
THE UPSHOT:
If you can write it in code,
you can run it on a blockchain.
Happy to
answer
questions!

Eris Industries - American Banker presentation deck.

  • 1.
    Private and confidential.Images and text (where applicable) copyright Eris Industries Limited, 2015. What’s wrong with crypto IT’S JUST SOFTWARE. Idealism, pragmatism, and “blockchain 2.0”
  • 2.
  • 3.
    Private  and  Confiden.al3 Most people look at blockchains like this
  • 4.
    Private  and  Confiden.al4 We look at blockchains like this
  • 5.
    Private  and  Confiden.al5 Our theory: mathematical infrastructure will replace physical infrastructure Current platform architecture requires that each market participant runs all of their own standalone human and machine infrastructure. This is a nightmare, and extremely expensive, to scale. BUT What if we could run shared data infrastructure without the multiple- redundant, hierarchical, centralised points of failure?
  • 6.
    Private  and  Confiden.al6 Our theory: blockchains Blockchains are distributed databases that house protocols for distributed data management Blockchains allow for high verifiability, systemic resiliency, ease of use, and low operating costs out of the box
  • 7.
    Private  and  Confiden.al7 Our theory: smart contracts Smart contracts are complex coded instructions which almost any blockchain is able to run and execute Blockchains aren’t magical internet money machines - they’re just software and will do exactly what we tell them to do What Bitcoin does for clearing and settlement, smart contracts can do for virtually any other business process
  • 8.
    Private  and  Confiden.al8 Addressing some common misconceptions “Mining” “Decentralisation” “Network effects”
  • 9.
    Private  and  Confiden.al9 MINING Is not required to validate transactions Is not (always) required to secure the chain (depends on chaintype in question & system design) - - - Is one of many possible security strategies Is designed to incentivise nodes to propose valid blocks when no-one is in charge
  • 10.
    Private  and  Confiden.al10 DECENTRALISATION Reverses cause and effect Does not work within existing legal paradigms Causes more commercial problems than it solves
  • 11.
    Private  and  Confiden.al11 NETWORK EFFECT I’ll get to that in a bit.
  • 12.
    Private  and  Confiden.al12 What we do Eris makes smart contracts easy to use. You can use a blockchain and explore smart contracts’ potential in your organisation Without needing to use a cryptocurrency Without paying anything to anyone Without being restricted to any one innovation
  • 13.
    Private  and  Confiden.al13 DEFINITIONS: WHAT IS A BLOCKCHAIN?
  • 14.
    Private  and  Confiden.al14 How the internet currently works
  • 15.
    Private  and  Confiden.al15 On somebody else’s (central) server
  • 16.
    Private  and  Confiden.al16 Blockchains: no servers, simple hardware
  • 17.
    Private  and  Confiden.al17 REDEFINING THE BLOCKCHAIN: JUST ANOTHER DISTRIBUTED DATABASE 1) distributed rulebooks 2) that track changes made to them 3) where write permissions are controlled by public-private key cryptography and 4) as a result, we can be fairly certain that something which is on a blockchain belongs there. (Sort of like French law actually)
  • 18.
    Private  and  Confiden.al18 Blockchains give us verifiable data. 1) Signature rules - tell ‘em what you’re gonna say Let’s agree on our ability to write to the data set. 2) Network rules - say it Let’s agree how we communicate with each other. 3) History rules - tell ‘em what you said Let’s agree on what the world-state of our data is and was, with the ability to easily check whether tampering has occurred.
  • 19.
    Private  and  Confiden.al19 RULE 1: TELL ‘EM WHAT YOU’RE GONNA SAY Effectively: users’ rules of the game; pre-defined access permissions Who can broadcast transactions? What actions can a user perform? How do they go about “spending” it? Can I reference data “offchain?”
  • 20.
    Private  and  Confiden.al20 RULE 2: SAY IT Open standard for common communication to achieve a common goal What can we say? What do words mean? Who do we listen to?
  • 21.
    Private  and  Confiden.al21 RULE 3: TELL ‘EM WHAT YOU SAID Also known as the “consensus protocol” Agreeing the truth What has been said? Who has said it? Is the record correct? “The dragon that eats its own tail:” what has happened (past) determines what can happen (now and future)
  • 22.
    Private  and  Confiden.al22 PUT IT ALL TOGETHER =" Mais,!c’est!en!français…"
  • 23.
    Private  and  Confiden.al23 TRANSLATE IT INTO ENGLISH
  • 24.
    Private  and  Confiden.al24 Hey, presto. That’s a blockchain application.
  • 25.
    Private  and  Confiden.al25 What Bitcoin demonstrated about the blockchain (as compared to other distributed database types) Security Verifiability Resiliency SIMPLICITY & EASE OF USE
  • 26.
    Private  and  Confiden.al26 Permissioning simply makes these qualities commercially viable. Accountability. Controllability. Repeatability. Reversibility.
  • 27.
    Private  and  Confiden.al27 Permissioning means that blockchain solutions can be engineered… to do exactly what you want them to do
  • 28.
    Private  and  Confiden.al28 DEFINITIONS: WHAT IS A SMART CONTRACT?
  • 29.
    Private  and  Confiden.al29 Nick Szabo, 1994 Quote courtesy of Tim Swanson’s presentation entitled “Defining Smart Contracts.”
  • 30.
    Private  and  Confiden.al30 Richard Gendal Brown, 2015 Quote courtesy of Tim Swanson’s presentation entitled “Defining Smart Contracts.”
  • 31.
    Private  and  Confiden.al31 Casey Kuhlman, 2015 “A smart contract is a script which allows for the cryptographically verifiable execution of code over cryptographically verifiable data.”
  • 32.
    Private  and  Confiden.al32 Why this definition makes sense Blockchains aren’t ledgers, they’re data stores Blockchains = verifiable data (state) Smart contracts = verifiable execution of code (write) HP: “The contract is the transaction” “The marmot is the contract”
  • 33.
    Private  and  Confiden.al33 What do all these definitions have in common? Characteristics: Scripts with state Almost any blockchain capable of running them Benefits: Can describe more complex data driven-processes Signature schemes apply to arbitrary data Limitations: Do not “self-enforce” (or “self-execute”) Work best when value is extrinsic to the data structure
  • 34.
    Private  and  Confiden.al34 HOW DO I USE SMART CONTRACTS?
  • 35.
    Private  and  Confiden.al35 Example: distributed Reddit (June 2014)
  • 36.
    Private  and  Confiden.al36 Example: People’s Republic of DOUG (June 2014)
  • 37.
    Private  and  Confiden.al37 Example: distributed YouTube (March 2015)
  • 38.
    Private  and  Confiden.al38 Examples: live pilots with MFIs Watch this space.
  • 39.
    Private  and  Confiden.al39 WHO’S INTERESTED?
  • 40.
    Private  and  Confiden.al40 Basically everyone
  • 41.
    Private  and  Confiden.al41 Integrators, developers, consultants, think tanks With the exception of marmcorp.com, no actual marmots are building with the Eris platform presently.
  • 42.
    Private  and  Confiden.al42 Other startups using similar technology
  • 43.
    Private  and  Confiden.al43 NETWORK EFFECT (I was saving this for later, remember?) Market ≠ Network Like running the Facebook playbook for Enterprise Linux.
  • 44.
    Private  and  Confiden.al44 HOW SHOULD WE CHANGE OUR THINKING?
  • 45.
    Private  and  Confiden.al45 To begin with Blockchains are not a scarce resource
  • 46.
    Private  and  Confiden.al46 Consequences Dramatic expansion in feasible, application-specific blockchain use-cases Shift of emphasis away from money, payments and “assets”, and towards process automation and data management
  • 47.
    Private  and  Confiden.al47 Cryptocurrency is only one application of blockchain technology. CRYPTOCURRENCY RULE 1 Open to all Evades government controls CRYPTOCURRENCY RULE 2 Distributed architecture = resilient to interference/ destruction CRYPTOCURRENCY RULE 3 Relies on competitive “mining” and awards “Bitcoins” etc Process is automatic, no central third party required Fraud difficult (but not impossible)
  • 48.
    Private  and  Confiden.al48 Getting away from the protocol and into the application: a how-to guide. MyChain Rule 1: Must be controllable in every respect All write permissions must be accessible through P/P key crypto In 99.99% of cases in finance, cannot be open/fully public Can talk to my other databases MyChain Rule 2: Cryptocurrency got this mostly right MyChain Rule 3: Change any aspect of the system on command Commercial standards of data security/certainty needed
  • 49.
    Private  and  Confiden.al49 HOW TO AVOID “PUT IT ON A BLOCKCHAIN” SYNDROME
  • 50.
    Private  and  Confiden.al50 STEP 1: DEFINE THE PROBLEM Does a blockchain solve a problem I have? YES: Coordinating actions of independent actors Simplifying multiple processes into single process Timely verification is paramount (e.g. settlement) Reducing supervision and oversight cost Need to scale without (much) hardware
  • 51.
    Private  and  Confiden.al51 DOES THIS SOLVE A PROBLEM I HAVE? NO: Requires speed (blockchains are comparatively slow) Requires heavy computation (blockchains are passive) Is fully automatic anyway (order of magnitude improvement harder to achieve; though blockchains could still be useful qua secure open standard)
  • 52.
    Private  and  Confiden.al52 STEP 2: DESIGN YOUR APPLICATION Source: “Solidity, Part 1: an Introduction to Smart Systems of Smart Contracts.” https://eng.erisindustries.com/tutorials/2015/03/11/solidity-1/
  • 53.
  • 54.
    STEP 4: ITERATE Because thecircumstances change Because business changes Because you’ll screw up Because you’ll improve
  • 55.
    Private  and  Confiden.al55 TO RECAP: Public blockchains = neat Permissioned blockchains = neat for commerce Smart contracts FTW in either case Eris helps you manage your smart contract applications, no matter the chain
  • 56.
    Private  and  Confiden.al56 THE UPSHOT: If you can write it in code, you can run it on a blockchain.
  • 57.