Personal focus on § Mobile & web-based application architectures § Interoperability, cross-device § Pragmatic end-to-end solutions § Cloud-native & serverless architectures § Independent Microsoft Regional Director § Microsoft MVP for ASP.NET (Architecture) ASPInsider, AzureInsider § Google GDE for Web Technologies [email protected] @christianweyer https://www.thinktecture.com Christian Weyer & Thinktecture Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
Doe 1 Feb 1960 0151-123 123 123 John Doe 1 Feb 1960 Fax, email, letter, ... SMS, email, letter, ... Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
Doe 1 Feb 1960 0151-123 123 123 John Doe 1 Feb 1960 Fax, email, letter, ... SMS, email, letter, ... Well, for us everything seems ok. Please ask the others. ? Well, for us everything seems ok. Please ask the others. Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
Ethereum, Bitcoin, ... Private Blockchains Telco E Telco C Telco A Telco F Telco G Telco B Telco D BNA Telco X Industry consortiums, governments, ... ? ! Telco X Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
Public blockchains and mining costs For transaction processing? A A • Proof-of-Work, but fortunately there are alternatives Figuring out who may create the next block? B Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
access rights are controlled; bad actors can be removed from network • No Proof-Of-Work mining necessary, but byzantine-fault tolerant signature-based schemes (Proof-of-Authority) • Costs are of a magnitude lower compared to Public • Transaction numbers much higher than with Public • Optional transaction privacy by reduced visibility (only participants in a TX receive it) • Medium to long term: interconnectivity between public chains and multiple, independent private chains E C A F G B D BNA X Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
changed or deleted at a later time #3 – What's in a block? (In practice, these are machine readable transaction records) The verified customer John Doe, born on Feb 1st, 1960, wants to transfer his number 0151-123 123 123 from Telco A to us Signed: Telco B We're OK with this transfer Signed: Telco A Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
owner: "TelcoA", encryptedCustomerData: "0xe2cbcf5f890afabc4dbd236d19f949db 05fcec2155..."} Signed: Telco B Encrypted with the public key of Telco A Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
"phone":"0151-123123123", owner: "TelcoA", signedScannedContractHash: "0x80ebe76679b4812cde61d555c9026...", encryptedCustomerData: "..."} Signed: Telco B "I've got a PDF here (which I'm not showing right now) with this hash" • To later prove existance and integrity of a piece of information at the time of block creation Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
"phone":"0151-123123123", owner: "TelcoA", externalDataHash: "0x5489b348f7a433...", } Signed: Telco B A hash to data which is sent directly to receiver (off-chain) • To ensure privacy: data is sent directly to the receiver without being shared with the network Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
valid? Validity of Transactions? We're ok with the transfer of number 0151-123 123 123 to Telco A Signed: Telco B Telco C WAIT! 0151-123 123 123 is not yours, but ours! • Laws, contracts, penalty payments (post-fact) • Or with technical solutions (pre-fact) Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
== msg.sender) { owner[number] = transferTarget; } else throw; } owner[number] == msg.sender owner[number] = transferTarget; Number Owner 0151123123123 Telco C 01511111111111 Telco A 01511111111112 Telco Z We're ok with the transfer of number 0151-123 123 123 to Telco A Signed: Telco C Cryptographic check State is changed OK Number Owner 0151123123123 Telco A 01511111111111 Telco A 01511111111112 Telco Z Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
independent participants? • No central authority? • No asymmetric power concentration? • Is everyone participating voluntarily? b) Do you need transparent and immutable shared data? c) Do you need trusted shared code execution? #5 – Can blockchains support my use case? Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
hash of your private documents or data on a blockchain • Technical proof of integrity and existence of documents and data at a certain point in time • Relatively easy to implement, quick ROI • No – or only small – focus on smart contracts Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
transparency • States of processes managed via blockchain • Digitization of paper processes between companies • E.g. Phone number porting Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
and markets • Reality check: Increased complexity due to the number of stakeholders Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
• Customers: better premiums • Insurer: competitive advantage • Carsharing provider: competitive advantage; maybe commission • Challenges • GDPR-conforming data processing • Scaling to lots of parties on all sides (no point-to-point interfaces) • Data should survive bankruptcy of a party (no on-demand generation) Idea: Case: Accident-free carsharing KMs per year Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
947989834 5345534524 958458205 755345… 9447757234 2349348572 345580923 84949283… 209389084 923840982 342394820 9348934… Customer Publication of signed data, encrypted with the public key of each customer Customer can decrypt her data at any time. Nobody else can. May 2018 Cust 1122 – 97 km - Provider1 June 2018 Cust 1122 – 535 km - Provider1 Customer can pass data to third parties after decryption. Even if the creator of the data does not exist anymore. (Ultimate data sovereignty) Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
provider #2 Rental car provider Insurer 2 Insurer 3 0304... 4586... 6436... 9384... 5463... 5854... … Feb 2018, 50 km, Stadt- mobil Feb 2018, 25 km, DB March 2018, 1534 km, Sixt Transfer by customer! Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
are created according to a consensus algorithm 2. Two different types of network: private and public (differ in consensus, transaction privacy, throughput, ...) 3. Blocks consist of immutable, signed statements called transactions 4. Smart contracts are shared program code, triggered by transactions; nothing more and nothing less 5. Blockchain use cases are based on decentralization The Five Things A Block- chain Opera- ting Models A Block Smart Con- tracts Use Cases Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019
decentralized to use decentralized technology. If your business model is more „like a database“, use a database. Put an API in front. It's much simpler. (YAGNI) Blockchain is cool (technology)! Wichtigste Fakten & sinnvolle Use Cases – jenseits des Hypes Blockchain in 2019