what should we learn from nakamoto s blockchain
play

What Should We Learn From Nakamoto's Blockchain? Roger Wattenhofer - PowerPoint PPT Presentation

What Should We Learn From Nakamoto's Blockchain? Roger Wattenhofer ETH Zurich Distributed Computing Group Not Me! Blockchain: The Biggest Story in Distributed Systems Since the Internet?!? Cryptocurrencies Blockchain So What


  1. What Should We Learn From Nakamoto's Blockchain? Roger Wattenhofer ETH Zurich – Distributed Computing Group

  2. Not Me!

  3. Blockchain: The Biggest Story in Distributed Systems Since …

  4. … the Internet?!?

  5. Cryptocurrencies

  6. Blockchain

  7. So What Is a Blockchain?

  8. Blockchain Distributed Systems & Cryptography (1982) (1976)

  9. Blockchain

  10. Transaction 4 5 1

  11. Why the Hype?

  12. Let’s Dig Deeper!

  13. Blockchain Persistence Fault-Tolerance NIL NIL Immutable Crash Provable Byzantine

  14. Blockchain Speed Throughput Eventual 10 tx/s Strong 10k tx/s Immediate 10m tx/s

  15. Blockchain Scalability 10 nodes 100 nodes 1000 nodes

  16. Energy Consumption

  17. Proof of Work � Energy/Hash ≈ 1.3 GW Hashrate 13 � 10 9 GH/s 0.1 J/GH

  18. Economic Incentives Market / Energy Value ≈ 19 GW $20k/BTC 12.5 BTC $0.08/kWh 6/h

  19. Upper Bound 19 GW Reality? Well… Lower Bound 1,3 GW

  20. Maybe Around 5 GW

  21. Blockchain Scalability Energy 10 nodes Country 100 nodes Village 1000 nodes Server Room

  22. What About Privacy?

  23. It’s Complicated.

  24. Privacy Operator World Open PoW

  25. The Seven Blockchain Dimensions Speed Persistence Privacy

  26. The Seven Blockchain Dimensions Speed Persistence Privacy

  27. Plenty of Research Dimensions

  28. piChain

  29. piChain: When a Blockchain Meets Paxos = +

  30. piChain: When a Blockchain Meets Paxos = + +

  31. Transaction

  32. Block

  33. parent depth

  34. slow medium quick

  35. New Transaction: Reaction Time wait wait quick medium slow time

  36. State Transitions quick medium slow seen : either deeper or by

  37. Self-Healing healthy

  38. Self-Healing

  39. committed

  40. Truncated Paxos ack time *and next propose

  41. Normal Paxos

  42. A Typical Example

  43. piChain vs. Raft similar essentially same goals simple e.g., no explicit leader election silent no msg when no tx, no heartbeat scalable O(1) msgs per node per tx

  44. Blockchain Persistence Fault-Tolerance NIL NIL Immutable Crash Provable Byzantine

  45. Blockchain Speed Throughput Eventual 10 tx/s Strong 10k tx/s Immediate 10m tx/s

  46. Blockchain Scalability Energy 10 nodes Country 100 nodes Village 1000 nodes Server Room

  47. Fundamental Problem Every Node Sees Every Transaction

  48. Payment Networks

  49. Payment Network

  50. Hashed Timelocked Contract (HTLC)

  51. HTLC Example ( sells to ) 3. “Send 6. “Send money if r money if r is known at time 4” is known at time 1” 7. Use 1. Generate secret r random to access 4. “Send secret r good 5. “Send money if r money if r is known 2. Send is known at time 3” hash( r ) to at time 2”

  52. Single Hop in Network

  53. Duplex Micropayment Channels (Example for Smart Contract)

  54. Duplex Micropayment Channel 5 10 5

  55. Duplex Micropayment Channel 5 T=100 5 5 10 5

  56. Duplex Micropayment Channel Blockchain 5 T=100 5 5 10 5

  57. Duplex Micropayment Channel Blockchain 5 T=100 5 5 10 5

  58. Duplex Micropayment Channel Blockchain 5 T=100 5 5 10 5 6 T=99 4 [Decker,W,2015]

  59. Duplex Micropayment Channel Blockchain 5 T=100 5 5 10 5 6 T=99 4 Channel must be renewed often?

  60. Duplex Micropayment Channel Blockchain 5 Δ T=100 5 5 10 5 6 Δ T=99 4 Relative timelocks to keep channel alive forever! But only 99 transactions?

  61. Duplex Micropayment Channel Δ T=20 ΔT =20 ΔT =20 Δ T=19 Δ T=20 ΔT =19 Δ T=19 Δ T=20 ΔT =19 ΔT =20 Δ T=19 Δ T=20 ΔT =19 Δ T=19 [Decker,W,2015]

  62. HTLC Revisited 5 Blockchain T=100 5 5 4 T=99 10 5 can be spent 5 by blue with secret r or 1 by green after 3 days 4. “Send money if r is known at time 3”

  63. HTLC Revisited 5 Blockchain T=100 5 5 4 T=99 10 5 can be spent 5 by blue with secret r or 1 by green after 3 days 4 T=98 4. Send 6 money if r is known at time 3

  64. Solved?

  65. Still Too Many Channels!?

  66. Each and Every Channel … needs two transactions on blockchain … has locked-in funds by both parties

  67. Each and Every Channel … needs two transactions on blockchain 200-800M channels only … has locked-in funds by both parties all my bitcoins are locked-in… sad.

  68. Blockchain Space Blockchain Space ~ Number of Signatures so far 4 signatures for every channel Funding Settlement

  69. Locked Funds ? ? ? ? A node wants to make connections… Where does it lock the funds?

  70. Multi Layer Networks 5 T=100 5 T=100 ... 6 T=99 ... 4 5 ... 5 ... 5 [Burchert, Decker, W 2017] ... T=99 5 ... 5 ... ... ... Channel funding layer Payment network layer

  71. Multi Layer Networks ... Δ T =100 ... ... 5 ... 5 ... 5 ... Δ T =99 5 [Burchert, Decker, W 2017] ... 5 ... ... ...

  72. Multi Layer Networks ... Δ T =100 ... ... 5 ... 5 ... 5 ... Δ T =99 5 [Burchert, Decker, W 2017] ... 5 ... 5 ... 5 ... Settlement 5 Transaction 5 5

  73. Multi Layer Networks ... Δ T =100 ... ... 5 ... 5 ... 5 ... Δ T =99 5 [Burchert, Decker, W 2017] ... 5 ... 5 ... 5 ... Settlement 5 Transaction Actual channels never reach the 5 blockchain! 5

  74. Blockchain Transactions 4 signatures per old channel 5 5 2 signatures per user 5 5 new 5 5 independent of 5 5 channels 5 5

  75. Are We Finally Done?!?

  76. Yes, unless you have Bitcoin Cash…

  77. Blockchain Persistence Fault-Tolerance NIL NIL Immutable Crash Provable Byzantine

  78. Blockchain Speed Throughput Eventual 10 tx/s Strong 10k tx/s Immediate 10m tx/s

  79. Blockchain Scalability Energy 10 nodes Country 100 nodes Village 1000 nodes Server Room

  80. Summary

  81. Thank You! Questions & Comments? Thanks to my co-authors Conrad Burchert Christian Decker www.disco.ethz.ch

Recommend


More recommend