This document discusses blockchain and enterprise IT, dispelling myths around distributed ledgers. It provides an overview of blockchain concepts like data integrity, actors, and public vs private blockchains. It also includes decision diagrams to help determine if a blockchain is needed and compares databases to blockchains. Example use cases for blockchains are listed such as supply chain management. Considerations for blockchain projects like requirements and limitations are also covered.

1. Blockchain &
Enterprise IT
Dispelling the myths around
distributed ledgers

2. Max Mortillaro
Partner & Principal Analyst, TECHunplugged B.V.
• Veteran Tech Field Day Delegate
• VMware vExpert 2013-2017
• Nutanix Technology Champion 2017
• www.kamshin.com
• www.techunplugged.io
• @darkkavenger

3. What this presentation ISN’T about
• Bitcoin
• Cryptocurrencies
• Investment
• Mining
• AI
• The Singularity
• Etc. etc.

4. Let’s use a
blockchain…

5. Trust

6. Blockchain Concepts
Data integrity (immutability)
Actors (how many parties interacting)
Disintermediation
Transactional dependency
Public/Private blockchain
Permissionless vs permissioned

7. Decision Diagram #1
Do I need a
blockchain?
No

8. Decision Diagram #2
Database
Store State?
Multiple
parties?
Trusted
Intermediary?
Actors
Trusted?
Public
Auditing?
Permissioned
Private
Permissioned
Public
Permissionless
Public
NO NO YES
Actors
Known?
YES NOYES
YES
NO
YES
NO NO
YES

9. Database vs Blockchain
Attribute Database Permissioned
Blockchain
Permissionless
Blockchain
Validation mechanism None BFT PoW or PoS
Throughput (I/O) Very High High Low
Latency Low Medium High
Management Central Decentralized Decentralized
BFT = Byzantine Fault Tolerance
PoW = Proof of Work (Mining)
PoS = Proof of Stake (Ownership, election mechanism)

10. Use cases
• Supply Chain Management
• Interbank Payments & Settlements
• Proof of Ownership
• Decentralized Autonomous Organizations
• E-Voting / E-Government

11. Considerations
• Have a good rationale for jumping into a blockchain project
• Don’t reinvent the wheel
• Put requirements first, scope etc. -> like in a « normal » project!
• Be aware of potential limitations
• Compute Power for Public Permissionless with PoW
• Throughput requirements (TPS / Transactions Per Second)
• Don’t be afraid to explore, PoCs are here for that
• If it doesn’t works, fail fast

12. References
• NISTIR 8202 (Draft) – « Blockchain Technology Overview »
(https://csrc.nist.gov/publications/detail/nistir/8202/draft)
• « Do you need a blockchain? », Karl Wüst, Arthur Gervais
(https://iohk.io/research/papers/#MNP2DS39)
• SPECTRE: Serialization of Proof-of-work Events: Confirming Transactions via
• Recursive Elections (https://eprint.iacr.org/2016/1159.pdf)