This presentation was delivered to the sold-out Ethereum.nz events on the 17th & 19th May 2016.
Blockchain for Enterprise:
•Exponential Tech & Macro
•5 Pillars / 3 Layers
•Solution Designs Examples
•Standards & Protocols
•Conclusion
Starting off by identifying the behavior of 'Exponential' technology and digging into the Macro-view of Blockchain's evolving out of it's early 'infrastructure building' days.
We take a look at the '5 Pillars & 3 Layers to Enterprise Blockchain Solution Design', breaking down what goes where and how to start.
Followed by examples of solutions design in Banking, Cross-Border Payments & Supply Chain.
Concluding with a comparison to the early internet days, where protocols and standards are continually evolving and what this means for Blockchain design considerations today.
If Blockchain Technology Interest you - please see BraveNewCoin.com for News, Analysis, charts, research and much more resources.
20. The 5 Pillars & 3 Layers
to Enterprise Blockchain Solution Design
21. Blockchain Considerations
• Bitcoin does 220m Transactions Per Year.
• Ethereum has a dynamic scaling capacity.
• Customer Data Privacy & Security.
• Legacy Infrastructure is not going to be
scrapped.
23. 1. Permissioned/Private
Writing records is exclusive to members, third
parties can be granted read access, with the
general public excluded. The permissions
architecture goes beyond ‘access = everything’
and allows third party access to specific raw
data, as deemed appropriate, for
interoperability and application requirements.
24. 2. Decentralized/P2P
Allowing for equal control over the shared
database between all permissioned
participants and of equal importance;
distributing the number of full copies of the
ledger to maximize probability that there will
always be a complete record in existence and
available for those with permissions to access.
25. 3. Immutability & Data Integrity
Records are guaranteed to be
cryptographically secure, with no possibility
for bad actors to threaten data integrity.
26. 4. Scalability
The ability to secure trillions of transactions or
records without compromising the networks
synchronization, security, accessibility or data
integrity.
27. 5. Security
Support for data encryption and the
management & enforcement of complex
permission settings for participants and 3rd
parties.
29. Blockchain Layer:
Used for: 'Pointers‘
Pillars: #2 - Decentralized/P2P, &
#3 - Immutability & Data Integrity
The Blockchain Layer doesn't
need: Business Logic (complex
permission structures), Data
Storage, etc
30. Data-Store Layer:
Used for: Encryption, Business
Logic (permission structures), Data
Storage, etc
Pillars: #1 - Permissioned/Private,
#4 - Scalability & #5 - Security
The Data-Store Layer doesn't
need: Open-Access or limited
transaction payloads due to block
sizes or other public blockchain
constraints.
32. Application Layer:
Used for: Processing the first two
layers into a useful business
application.
Pillars: None
The Application Layer doesn't
need: Any of the Blockchain or
Data-Store layer functions or
considerations.
34. Where does Ethereum & Smart Contracts fit in?
Ethereum is an application platform on top of blockchains (With
it’s own Blockchain) - like we have java and other application
platforms on top of regular databases. Choose and replace the
application platform to fit use-cases.
37. Smart contracts = Business Logic
If blockchains are good at making sure data is accurately replicated across untrusted entities, smart contracts are
good at making sure logic is accurately executed across untrusted entities.
As far as current ways of ensuring that exactly the same logic is followed between two entities, our best tool is
automatic reconciliations of data before and after a process. With blockchains and smart contracts, the technology
guarantees the process.
39. Bank Feeds on the
Blockchain?
• Bank writes an encrypted data record for
Customer[c] to the Private Data Store.
• Bank broadcasts a transaction under
Customer[c]’s address to the Blockchain with a
pointer to the data record.
• Third-party [Intuit] was monitoring for
transactions under Customer[c]’s address and
reads the pointer.
• Third-party[Intuit] initiates a key exchange with
the Bank to retrieve a shared secret for the data
record.
• Third-party[Intuit] uses the shared secret to
decrypt the data record and can now read the
transactional data from the Private Data Store.
45. 25+ years ago:
• Remember “Open Systems Interconnection,” (OSI)?
• Supported by Countless Countries, Engineers &
Companies
• “OSI is a beautiful dream, and TCP/IP is living it!”
46. Conclusion:
• Enterprise Blockchain – Separate Design into
Layers.
• Blockchain is Exponential Technology – Evolving
fast.
• Networks ALWAYS end up demanding inter-
operability:
• Have an early plan with the future in mind.