network partitioning e ff ects on ripple transactions
play

Network Partitioning E ff ects on Ripple Transactions Yoan Martin - PowerPoint PPT Presentation

Network Partitioning E ff ects on Ripple Transactions Yoan Martin 1 Todays menu What is Ripple? Why is it interesting? Attacks Analysis 2 What is Ripple? Global Payments Network RippleNet vs XRP Gateway


  1. Network Partitioning E ff ects on Ripple Transactions Yoan Martin � 1

  2. Today’s menu • What is Ripple? • Why is it interesting? • Attacks • Analysis � 2

  3. What is Ripple? • Global Payments Network • RippleNet vs XRP • Gateway • Entry Point • Ripple Bank � 3

  4. Why is it interesting? • More than 200 financial institutions • ~20’000’000 USD sent by hour • Take place on internet � 4

  5. What is the network? � 5

  6. Network � 6

  7. What is the network? � 7

  8. Attacks • What if an AS is malicious? • What can it do? • Dropping the traffic • BGP H ij acking � 8

  9. Tra ffi c dropped � 9

  10. Tra ffi c dropped � 10

  11. BGP Hijacking B A � 11

  12. BGP Hijacking B A � 12

  13. BGP Hijacking B I know B! A � 13

  14. BGP Hijacking B A � 14

  15. How to measure the e ff ect? • Build the Ripple Network • Ripple API • Caida • Use previous transactions • Replay transactions when an attack occurs � 15

  16. Build RippleNet Ripple API, Gateways data AS AS relationships AS with a Gateway � 16

  17. Map Result � 17

  18. Transactions • Account A sends 100 XRP to account B • Some transactions have gateways data • Account A sends 100 XRP using Gateway G to B • Account B receives 100 XRP using Gateway H from A • Keep only transactions with matching Gateways � 18

  19. Simulation : tra ffi c dropped A sends 100 XRP to B A sends 100 XRP to B D sends 10 USD to A D sends 10 USD to A C sends 4 EUR to B C sends 4 EUR to B … … � 19

  20. Simulation : tra ffi c dropped • If == , transaction is complete • If != , transaction is rerouted • If no , transaction is lost � 20

  21. Example of results Completed Rerouted Lost Amazon 10% 10% 80% AT&T 30% 20% 50% China 60% 30% 10% Telecom Swisscom 30% 30% 40% � 21

  22. Simulation: BGP Hijacking A sends 100 XRP to B D sends 10 USD to A C sends 4 EUR to B … � 22

  23. Simulation: BGP Hijacking • If == , transaction is complete • If != , transaction is rerouted � 23

  24. Example of results Completed Rerouted Amazon 90% 10% AT&T 60% 40% China Telecom 20% 80% Swisscom 30% 70% � 24

  25. Real Results • Transactions analysis • Which ASes are the most dangerous? • What is the effect on the Ripple network? � 25

  26. Transactions analysis • % of transactions with AS as sender or receiver • 13335 is Cloudflare (US) • 19551 is Incapsula (US) � 26

  27. Which ASes are dangerous? Tra ffi c dropped • % transactions lost corresponds to transactions distribution • Lost if gateways in corrupted node • Never lost if intermediaries • Always possible to find a path � 27

  28. Which ASes are dangerous? Tra ffi c dropped • Little % of rerouted transactions • Certainly due to transactions distribution • 553 is Belwue (DE) • Connections with 680 ISP • Switch, Swisscom � 28

  29. Which ASes are dangerous? BGP Hijacking • Many ASes can corrupt the network • Long list of ASes reach almost 40% of rerouted transactions � 29

  30. What is the e ff ect on Ripple? • Time analysis • On average low effect � 30

  31. Conclusion • Most of the transactions go through 2 ASes • Big impact if one of them is corrupted • BGP H ij acking has more effect than traffic dropped • Limitations of this analysis • Network only considers Gateways • Hence, only a few transactions are considered � 31

  32. Thank you for your attention � 32

  33. White gap? � 33

  34. BGP Hijacking : August ? � 34

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend