Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Blockchain als Architektur-Komponente – Fluch o...

Blockchain als Architektur-Komponente – Fluch oder Segen?

Mit dem Start der Bitcoin Blockchain im Jahr 2009 wurde der Welt eine verteilte Datenbank zugänglich, bei der nur im Konsens der Teilnehmer über den aktuellen Zustand bestimmt werden kann. Während der Use-Case einer unabhängigen Währung leicht zu greifen ist, fällt es uns bisweilen schwer, die Charakteristiken von Blockchains sinnvoll auf andere Anwendungen zu übertragen. In diesem Talk werden Sie lernen, welche Features die Blockchain einzigartig machen und unter welchen Umständen Sie davon profitieren können - aber auch wann Sie davon absehen sollten. Dieses Wissen wird Patrick Stürmlinger mit Ihnen anhand eines real existierenden Projekts zur Sicherung von Dokumentenarchiven anwenden und vertiefen.

Patrick Stürmlinger

November 19, 2019
Tweet

More Decks by Patrick Stürmlinger

Other Decks in Technology

Transcript

  1. Patrick Stürmlinger [email protected] @PSturmlinger Public vs. Private Blockchains • Public

    Blockchains are publicly accessable and readable • Private Blockchains are hosted by consortiums and only accessable to their members
  2. Patrick Stürmlinger [email protected] @PSturmlinger Blockchain Features Immutability No manipulation Distributed

    Ledger No Single Point of Failure Decentralized Governance Democracy Transparency Trust Permissionless Accessibility
  3. Patrick Stürmlinger [email protected] @PSturmlinger Database vs. Blockchain Database Public Blockchain

    Private Blockchain Stores data yes yes yes Cost cheap expensive cheap Performance fast slow - medium fast Designed for any kind of data Small data Small data Technical operation centralized distributed distributed Tamper proof no yes yes Transparency no yes yes Finality instant delayed delayed
  4. Patrick Stürmlinger [email protected] @PSturmlinger When To Use Blockchain • Timestamping

    data • Proof authenticity of data • If complete track record brings value • If additional trust brings value • To replace legacy systems Use blockchain • Storing private data • Data needs to be deleted • To store a lot of data • Data just for yourself • you’re just doing it for the buzz Do NOT use blockchain
  5. Patrick Stürmlinger [email protected] @PSturmlinger Lessons Learned • Network MUST NOT

    be in control of a single party A single party controlled blockchain loses it‘s value! • Network effect is crucial for many use cases Collaborate with as many partners as possible!
  6. Patrick Stürmlinger [email protected] @PSturmlinger Better control / overview about money

    flow Replaces legacy systems Better control / overview about money flow Decentralized governance brings value Use Cases Additional trust brings value Replaces legacy systems Decentralized governance brings value Decentralized operation brings value Need for high tx/s Cryptocurrencies
  7. Patrick Stürmlinger [email protected] @PSturmlinger Use Cases Additional trust brings value

    Complete track record brings value Decentralized governance brings value Loyalty Systems
  8. Patrick Stürmlinger [email protected] @PSturmlinger Use Cases Replaces legacy systems Additional

    trust brings value Complete track record brings value Decentralized governance brings value Art tracking
  9. Patrick Stürmlinger [email protected] @PSturmlinger Use Cases Replaces legacy systems Additional

    trust brings value Complete track record brings value Decentralized governance brings value Diamond supply chain
  10. Patrick Stürmlinger [email protected] @PSturmlinger Use Cases Data just for yourself

    Doing it for the buzz Single merchant food supply chain
  11. Patrick Stürmlinger [email protected] @PSturmlinger Use Cases Replaces legacy systems Additional

    trust brings value Complete track record brings value Decentralized governance brings value Timestamping data Industrie wide supply chain
  12. Patrick Stürmlinger [email protected] @PSturmlinger Example: Document Archiving • Vendor provides

    archiving system • Public administration puts historical data into the archive • Vendor guarantees permanent filing & authenticity • Archive secures a record of public data like contracts or historical relevant events Overview Goals Provide proof of authenticity Easy access to external auditors
  13. Patrick Stürmlinger [email protected] @PSturmlinger Example: Document Archiving Options Notary service

    to confirm data integrity on regular basis It works Expensive and complex Access barrier Single point of failure
  14. Patrick Stürmlinger [email protected] @PSturmlinger Example: Document Archiving Options Printing the

    archives merkle hash into a newspaper Public records Expensive and complex Access barrier
  15. Patrick Stürmlinger [email protected] @PSturmlinger Example: Document Archiving How it works

    Upload 1 Archive 2 Daily Merkle Tree 3 Database Store 4 Public Blockchain Store 5
  16. Patrick Stürmlinger [email protected] @PSturmlinger Example: Document Archiving Document 2 Document

    1 Document 3 Document 4 Hash(Doc 1) Hash(Doc 2) Hash(Doc 3) Hash(Doc 4) Hash(H1 + H2) Hash(H3 + H4) Merkle Root Hash(H1_2 + H3_4) Verification
  17. Patrick Stürmlinger [email protected] @PSturmlinger Conclusion • Have multiple parties •

    You want to proof sth. • Trust at the core of your business • Don‘t use it just because you can! [email protected] @PSturmlinger https://speakerdeck.com/pstuermlinger
  18. Patrick Stürmlinger [email protected] @PSturmlinger Proof of Existence & Proof of

    Authenticity Proof of Existence Proof of Authenticity Bonus: Proof of Owner-/Authorship Block #3 Block #4 Block #2 96179ec02b5f8376041f…