intro to r3 - meetupfiles.meetup.com/19726545/corda hyperledger london presentation… ·...

Intro to R3

05/12/16.

R3 Engineering

Secondary color palette

Dark Grey150 150 150

Light Grey209 211 212

Dark Red18936 40

Light Red247 150 121

Blue43121240

Light Blue112 179 255

tertiary colorpalette

Green0

15189

Light Green0

212 117

Orange255 1260

Light Orange255 187 94

Dark Yellow180 17030

Yellow24821413

How is R3 enabling collaboration?

Create a Product

Market it and sell it

Refine it (maybe)

Create a Consortium

Collaborate on requirements; open source

Build it together

70+ global institutions

1400 + passionate

people

Most Start-ups:

R3:




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

R3 Global Members




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Hype

POCs Early Scaled Deployments

Talk

Main StreamDeployments

Early Adoptions

ValueDefinition

Building Blocks

Collaboration

Tipping Point

Market Interfaces

“The Norm”

StandardsRegulationTechnology

GovernanceCollaboration

Bridging the gap towards mainstream adoption

We are here




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Consortium Projects

The Empire Strikes Back!

December 6th 2016.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Stuff we will cover• Interesting features

• Unusual design decisions

• Next steps

Caveat: will mix implemented vs pending work. Will call out what’s not coded with a *

p7.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

That’s us!

Corda @ HyperLedger London p8.

OK, so how does it work?




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Basics you must know• No block chains, no mining

• Permissioned networks

• JVM based

• Open source reference implementation, unfinished

• Tech white paper is a design doc





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Bitcoin-esque tx structure


• Ledger is composed of (output) states• Execution of code for both inputs and outputs• Signatures external to the transaction data• Platform checks signatures, contract code

only checks presence of pubkeys• Commands parameterise transactions• Key randomisation with separable identities*




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

p12.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

But with extras …


Transactions can have attachments.

Attachments are zip files referred to by hash. Can contain:

• Contract bytecode• Legal documents explaining what it’s meant to do• Static reference data (e.g. holiday calendars)• Identity certificates• Anything else

Attachments form a per-tx filesystem and files cannot overlap.

Attachments are deduplicated on the wire.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

But with extras …


Transactions are structured as a Merkle tree. Can selectively reveal different parts.

States (outputs) can contain arbitrary object graphs

(at present – may restrict this soon)

Encumbrances allow you to combine different contract logic.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Unusual design decision 1No broadcast: transactions resolved lazily

Consequence: DoS handling is simpler

Consequence: bulk data import is silent

Consequence: must specify where data is sentCorda @ HyperLedger London p15.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

P2P network structure• All communication bidirectional

• Messages organised into flows

• A “flow” is an uber-thread that survives process restarts, stored in the database

• Uses fibers behind the scenesHow?

p16.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Flows• Flows specify the identities to which messages are sent

• Flows are type safe

• Corda network is SMTP-like– Messages are buffered to disk and delivery is retried up to

the event horizon

• Flows can interact with people* and internal systems

• Protocol is AMQP/1.0 + TLS, node is services connected to an MQ broker





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Flows• Flows have progress tracking

• Flows can read/write to the node’s relational database

• Flows can invoke sub-flows

• Corda provides a standard library of flows for common tasks





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

SQL supportPity the fool who tries to build a block chain app!

New databases are hip but:

• How to analyse data in them?• How to combine with private data?• Don’t even think about migrating existing apps or

data …

Most platforms give you REST and then you’re aloneCorda @ HyperLedger London p20.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

SQL supportCorda built on the JVM

Embeds the H2 relational database. JDBC access.Support for other external DBs in future*

State schemas can be JPA annotated with conversion code in the smart contract

“Relevant” states written to DB tables

State schemas commonly contain slots for join keys





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

p22.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Notaries and consensus• Pluggable consensus algorithms

• “Notaries” can be/should be distributed

• Notary implementations:– Onebox: for local testing/dev work– Raft: robust against node failure, not malice– Above x2 for non-validating modes– In future, BFT-SMaRT*





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Deterministic JVMCorda contracts defined using restricted, cut down bytecode

Most features are gone, e.g.

• No threading or finalisers• No access to external data (files, networks, RNGs, clocks)• Object.hashCode modified to be derived from tx hash*• No native code• Bytecode instrumented to do cost accounting• Exception handlers adjusted to prevent thread termination• strictfp enforced everywhere• No invokedynamic• Class libraries bytecode rewritten as well

(+more!)Corda @ HyperLedger London p24.




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Client RPCPrimary comms is via Client RPC

• Small (~800 loc) RPC stack that operates over MQ

• Can marshal Rx observables: streaming of results is natural

• Can handle temporary connection problems, backpressure management*, buffering etc …

• Thin client library exposes reactive collections that can be directly bound to JavaFX UI and mapped/filtered/sorted

Functional, pipeline oriented programming.





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Experimental universal contractval one_touch = arrange {

actions {highStreetBank may {

"expire".givenThat(after("2017-09-01")) {zero

}}acmeCorp may {

"knock in".givenThat(EUR / USD gt 1.3) {highStreetBank.owes(acmeCorp, 1.M, USD)

}}

}}





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Lots more!• Novel design for client-side signing devices (e.g. TREZOR)*• Identity management*• Event scheduling• Type system for modelling nettable obligations, assets,

fungibility• Network permissioning infrastructure• Data distribution groups*


Corda: Next steps




Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

The 4 s’sUntil now: experimentation and design

Starting now: the road to production

• Security

• Serialisation

• Scalability

• Finishing the features





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

Privacy and scalability• Start random key usage once identity cert

management is done

• Novel privacy research in prototype phase that we will talk about more if/when it’s more mature

• Implement vault soft-locks and start load testing, eliminating bugs





Dark Red18936 40


Blue43121240



Green0

15189

Light Green0

212 117

Orange255 1260



Yellow24821413

p31.

Goal

API and protocol stability by

EOQ3 2017

intro to r3 - meetupfiles.meetup.com/19726545/corda hyperledger london presentation… ·...

Documents