Towards the internet of value & trust.
"To develop shared global compute infrastructure,
we must first understand the status quo of infrastructure,
...and how to change it accordingly."
Dimitri De Jonghe, lead developer of BigchainDB talking about blockchain technology beyond the financial sector.
2. @DimitriDeJonghe
● 2008 Master micro-electronics (KULeuven)
● 2013 PhD on applying machine learning to
micro-electronics design (KULeuven)
● 2014 Machine learning startups (sydelity, scriptbook)
● >2014 founding member ascribe.io / BigchainDB
○ ascribe.io - bitcoin blockchain for online licensing
○ BigchainDB - scalable blockchain database
○ IPDB Foundation - interplanetary database, public
BigchainDB for commons
○ Interledger co-chair - the internet of blockchains
Micro-electronics
Machinelearning
Blockchain
● Dimitri De Jonghe
Blockchain technologist & enthusiast
3.
4.
5.
6.
7.
8.
9.
10.
11. “My conclusion is that whatever you put on the
internet you lose it.
Maybe keep the rights, but lose the power over
it.”
-User on Shapeways blog (3D printing marketplace)
24. To develop shared global
compute infrastructure,
we must first understand the
status quo of infrastructure,
…and how to change it
accordingly.
25. To blockchain or not to blockchain?
● Need interaction with one or more parties?
● Do you want a crypto-secured shared single source of truth?
● Do you need apply and comply with a shared set of rules?
26. Status quo compute infrastructure
Modern apps use processing, file system, database
FILE SYSTEM
e.g. S3, HDFS
APPLICATION
PROCESSING
e.g. EC2, Azure
DATABASE
e.g. MySQL, MongoDB
PLATFORM
e.g. AWS, Google App Engine, Heroku
CONNECTNETWORKS
e.g.TCP/IP
27. Towards a decentralized compute infrastructure
FILE SYSTEM
e.g. S3, HDFS
APPLICATION
PROCESSING
e.g. EC2, Azure
DATABASE
e.g. MySQL, MongoDB
Bitcoin Blockchain?
PLATFORM
e.g. AWS, Google App Engine, Heroku
CONNECTNETWORKS
e.g.TCP/IP
28. Towards a decentralized compute infrastructure
FILE SYSTEM
e.g. S3, HDFS
APPLICATION
PROCESSING
e.g. EC2, Azure
DATABASE
e.g. MySQL, MongoDB
PLATFORM
e.g. AWS, Google App Engine, Heroku
CONNECTNETWORKS
e.g.TCP/IP
e-Cash/e-Gold
Bitcoin
29. Towards a decentralized compute infrastructure
FILE SYSTEM
e.g. S3, HDFS
IPFS, SWARM
APPLICATION
PROCESSING
e.g. EC2, Azure, Ethereum, Hyperledger, Tendermint, Lisk, Corda
DATABASE
e.g. MySQL, MongoDB
BigchainDB, IPDB
PLATFORM
e.g. AWS, Google App Engine, Heroku, Eris/Monax, BlockApps
CONNECTNETWORKS
e.g.TCP/IP,InterledgerILP
e-Cash/e-Gold
Bitcoin, zCash, Ripple,
Blockstream, Multichain
30. Decentralized Stack Interoperability
FILE SYSTEM
e.g. IPFS, SWARM
PROCESSING
e.g. Ethereum, Hyperledger, Tendermint, Lisk, Corda
DATABASE
e.g. BigchainDB, IPDB
PLATFORM
e.g. Eris/Monax, BlockApps
e-Cash/e-Gold
Bitcoin, zCash, Ripple,
Blockstream, Multichain
Protocols:
Interledger
IPLD
Hash Registry:
E.g uPort
Contract
Registry:
E.g dapp.registry
Oracles:
Push data
E.g. Oraclize
Backend
specific
OP-Codes
Configure stack: contract scripts, consensus, storage backends
31. 2016 onwards
● BaaS: Blockchain as a Service (Azure, Amazon, IBM, IPDB)
● Internet of value: connect blockchains and legacy (Interledger)
● Standardization: Asset definitions, comm. Protocols, API’s
● Borderless and instantaneous micropayments and exchanges
● Scalability: Big-data meets Blockchain (BigchainDB)
● Internet of things: digitization of real world assets
● Privacy: zero-knowledge proofs to mask transaction content
● Identity: e-governance, IoT identity on-chip
● ...
39. Status quo compute infrastructure
Modern apps use processing, file system, database
FILE SYSTEM
e.g. S3, HDFS
APPLICATION
PROCESSING
e.g. EC2, Azure
DATABASE
e.g. MySQL, MongoDB
PLATFORM
e.g. AWS, Google App Engine, Heroku
CONNECTNETWORKS
e.g.TCP/IP
40. ascribe: a partly decentralized app (DApp)
FILE SYSTEM
e.g. S3, HDFS
APPLICATION: ascribe.io
PROCESSING
e.g. EC2, Azure
DATABASE
e.g. MySQL, MongoDB
Bitcoin Blockchain
PLATFORM
e.g. AWS, Google App Engine, Heroku
CONNECTNETWORKS
e.g.TCP/IP
OP_RETURN: copyright + author + metadata/URIs
52. Swallow the WEB
ML Image Search
Analytics
How to get Provenance of COPIES?
53. whereonthe.net
Provenance of the COPIES
According to
WhereOnTheNet, Detail from
The Creation of Adam,
appeared on 4,548 websites
and 18,796 unique pages.
This image has had around 56
occurrences on Twitter, which
is less then 1% of all
occurrences.
54. Rogier van der Weyden, Portrait of a young Lady, around 1440/45, Staatliche Museen zu Berlin,
Gemäldegalerie
(Image: Public Domain)
Where is Portrait of a young Lady ?
60. Netflix uses 37% of Internet bandwidth
Using a modern distributed “big data” database
http://techblog.netflix.com/2011/11/benchmarking-cassandra-scalability-on.html
Writes / s vs. # nodes
62. 2 ways to scale up
Big data-fy blockchains
• Builds on man-decades of work
• Significant scalability hurdles
<or>
Blockchain-ify big data
• Builds on man-centuries (millennia?) of work
• Scalability challenges already resolved
• How to blockchain-ify? …
63. payment channels /
trust lines /
side chains (e.g. blockstream)
high-speed
trust line slow-speed sync
Big data-fy the blockchain
64. What’s the difference between a database and a csv file?
Querying. From M’s of records, find the relevant ones.
1 Line of standard code, optimized
vs
50-500 lines of slow custom code, unoptimized
65. How do “big data” databases scale?
Answer: Distribute storage across many machines, i.e. sharding
A “consensus” algorithm keeps
distributed nodes in sync.
66. Native assets
How to build a scalable blockchain database (BigchainDB)
1. Start with an enterprise-grade distributed DB, e.g. MongoDB
2. Engineer in blockchain characteristics
• Each DB node is a federation node
Decentralized /
Shared Control
• Append-only
• Chain hashes
Immutable /
Audit Trails
• “Own” = have private key
• Asset lives on the database
68. BigchainDB: Big Data meets Blockchain
- a blockchain database
Immutability
Decentralized Control
Native Assets
Scalable
Queryability
Operationalized
Traditional
Databases
Traditional
blockchains
BigchainDB
81. • For everyone, everywhere
• Free until heavy usage, then pay web service style
• Initial tech is BigchainDB
• Member caretakers will operate validating nodes
84. Taking the next step with blockchains
• Identify use cases, e.g. using tools here
• Validate use cases with blockchain experts
• Start experimenting, e.g github.com/bigchaindb
• Find the right expertise ;-)