DOCSLIB.ORG

Masters's Thesis Incentivized Delivery Network of Iot Software Updates

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Masters's Thesis Incentivized Delivery Network of Iot Software Updates Ben-Gurion University of the Negev Masters’s Thesis Incentivized Delivery Network of IoT Software Updates using gradual release Submitted By: Supervisor: Yechiav Yitzchak Prof. Asaf Shabtai A thesis submitted in fulfillment of the requirements for the degree of Master of Science in the DEPARTMENT OF SOFTWARE AND INFORMATION SYSTEMS ENGINEERING FACULTY OF ENGINEERING SCIENCES February 27, 2019 Ben-Gurion University of the Negev Masters’s Thesis Incentivized Delivery Network of IoT Software Updates using gradual release Submitted By: Supervisor: Yechiav Yitzchak Prof. Asaf Shabtai A thesis submitted in fulfillment of the requirements for the degree of Master of Science in the DEPARTMENT OF SOFTWARE AND INFORMATION SYSTEMS ENGINEERING FACULTY OF ENGINEERING SCIENCES Author: .............................................................................. Date ........27.2.2019 Suprvisor: ....................................... ...................................Date ........06/05/2020 Chairman of Graduate Studies Committee: ……………………..Date…… Abstract this work introduces IoTPatchPool Pay Per Piece -aschemethatenablesanincen- tivized distributed delivery network of IoT software updates. the scheme uses a decentralized storage network for reducing the load on the vendor when distributing patches towards IoT devices and eliminating central points of failure. Unlike existing peer-to-peer file-sharing networks that have a fundamental availability problem for unpopular files, our protocol utilizes blockchain-based smart contracts to incentivize independent peers, termed distributors, by means of cryptocurrency payments. A vendor of IoT devices deploys a smart contract with a deposit, which acts as a publicly verifiable binding bid for delivery of patches by pieces to a specific set of IoT endpoints. Distributors will compete for delivering updates to the desired IoT devices in exchange for cryptocurrency payments. We address the fair exchange problem between distributors and the consuming IoT devices by utilizing aa Pay Per Piece Payments protocol, the pay per piece is a form of a gradual release of a commodity where the commodity can be divided into small piece the sender and the receiver build trust as the transactions progress in rounds the permission-less nature of the framework can encourage the participation of a large number of dis- tributors, and thus facilitate a rapid scale-out of the system. Finally, we present and evaluate a prototype implementation combining the BitTorrent network with the cryptocurrency Ethereum. Keywords IoT Blockchain Patch Update Distributed ledger Ethereum Incentivized system 2 Acknowledgments would like to thank several people for supporting me in the work on this thesis. First, I would like to express my appreciation to my supervisor Prof. Asaf Shabtai, for the guidance, support, and brainstorming, he has given me all along this thesis. IwouldliketothankRonBitonforhissupportthroughoutthisprocessin consulting, examining new paths, and pushing the boundaries. Second, I would like to thank all my colleagues who I worked the framework leading to this thesis, Oded Leiba, Ron Biton, Asaf Nadler, Davidoz Kashi, and Ishai Wiesner. Third, I would like to thank Zur Ronen for his help and support in implementation. lastly many thanks to Telekom Innovation Laboratories at Ben-Gurion University for providing the supporting environment. 2 Contents Abbreviations 8 1Introduction 9 1.1 Background ................................ 13 1.1.1 Blockchain ............................. 13 1.1.2 Smart Contracts ......................... 14 1.1.3 zk-SNARKs ............................ 15 1.1.4 Zero-Knowledge Contingent Payments (ZKCP) ........ 16 1.1.5 Gradual release .......................... 16 2ResearchObjectives 18 2.1 Research Goal .............................. 18 2.2 Research Questions ........................... 19 2.2.1 RQ1: Defining a incentivized IoT patching protocol ...... 19 2.2.2 RQ2: Examining The economic model of the system ..... 19 3RelatedWork 20 3.1 General Architectures for IoT Patching ................ 20 3.2 Decentralized Storage Networks ..................... 22 4SecurityModel 25 4.1 Trust Model ................................ 25 4.2 Adversarial Model ............................. 26 4.3 Goals ................................... 26 3 5TheMainComponents 27 5.1 Decentralized storage network (DSN) .................. 27 5.2 Blockchain network ............................ 28 5.2.1 Vendor nodes ........................... 28 5.2.2 IoT nodes ............................. 29 5.2.3 Distributor nodes ......................... 30 6IoTPatchPool 32 6.1 Protocol .................................. 33 6.1.1 Setup ............................... 34 6.1.2 Contract publication ....................... 34 6.1.3 Update file initial seeding .................... 36 6.1.4 Update file exchange for a proof-of-distribution ........ 37 6.1.5 Reward claim for a proof-of-distribution ............ 39 6.2 Properties ................................. 40 6.3 Implementation .............................. 43 7Proposedframework:IoTPatchPoolPayperpiece 47 7.1 Alternative selection ........................... 49 7.2 Protocol .................................. 51 7.2.1 Setup ............................... 51 7.2.2 Contract publication ....................... 51 7.2.3 Update file initial seeding .................... 52 7.2.4 Update file Pay Per Piece exchange .............. 54 7.2.5 Reward claiming ......................... 55 7.3 Implementation .............................. 57 7.4 Evaluation ................................. 58 7.4.1 Properties ............................. 60 8Discussion 62 8.1 Common Requirements ......................... 62 4 8.2 Comparison ................................ 63 8.3 Economic Feasibility Analysis ...................... 69 9ConclusionsandFutureWork 73 5 List of Figures 6.1 IOTPatchpool High level architecture overview ......... 33 6.2 IOTPatchpool High level overview of the update protocol .. 40 6.3 IOTPatchpool: Outline of the IoT software update protocol 41 6.4 IOTPatchpool: The board used for our demonstration environment, consisting of 48 Raspberry Pi devices. .................. 45 6.5 IOTPatchpool: A screenshot capturing the user interface of the ven- dor’s server during the update process. ................. 45 7.1 IoTPatchPool Pay Per Piece High level architecture overview 49 7.2 IoTPatchPool Pay Per Piece sequence diagram ......... 56 8.1 Gas consumption comparison ...................... 65 8.2 Time (sec) to execute a Redeem transaction the Rinkeby Test net ................................. 67 8.3 time to execute first device update.timeinsecondsforupdating first device on both frameworks, IoTPatchPool on top part and IoTPatchPool Pay Per Piece on bottom part ........... 68 8.4 time to complete 100 IoT devices update.timeinsecondsfor completing 100 devices update, IoTPatchPool on top part and IoTPatchPool Pay Per Piece on bottom part ........... 68 8.5 Frameworks economic feasibility compared to alternatives ....... 72 6 List of Tables 8.1 Comparison between the IoTPatchPool and IoTPatchPool PPP frame- works ................................... 64 8.2 Summary of the main items and their size in both frameworks .... 68 8.3 A breakdown of the transactions costs ................. 71 7 Abbreviations DHT Distributed hash table DOS Denial of service DSN Decentralized storage network ECDSA Elliptic Curve Digital Signature Algorithm EVM Ethereum Virtual Machine IOT Internet Of Things IPFS InterPlanetary File System P2P Peer to Peer PPP Pay Per Piece ZCKP Zero-Knowledge Contingent Payment 8 Chapter 1 Introduction The Internet of Things (IoT) is a disruptive paradigm that continues to evolve. It is predicted that there will be a total of 26 billion connected IoT units by 2020.1 The prevalence of these devices makes them an ideal target for attackers, recently many high impact exploits have been demonstrated in practice [1, 2]. In order to de- fend devices from such vulnerabilities or recover from attacks, they must be patched with security updates. Concerns have been raised by users and manufacture alike that this need is often overlooked, and in practice, devices are patched much more rarely than they should [3]. This is in large part due to the slim profit margins of IoT manufacturers, and operational difficulties associated with the large-scale patching of devices. Another concern around the traditional way to distribute con- tent and in particular IoT software updates is the centralized nature of client-server architectures which typically rely on a large geographically and/or organizationally centralized cloud service. The increased amount of IoT devices and sensors, with their respective large amounts of data they broadcast and consume, can put a signif- icant burden on ISPs, inter-ISP business relationships, and the Internet backbone. Therefore, recent researches focused on shifting computation and data throughput to the edge, so that a large part of the data exchange can be performed within the boundaries of single ISPs [4, 5]. Moreover, such architectures impose large central points of failure and are subject to vulnerabilities such as natural disasters or local 1https://www.gartner.com/newsroom/id/3598917 9 outages. For instance, Amazon Web Services (AWS) control around 40% of the cloud-server market, and a recent outage in its US-East-1 region (Ashburn) caused asignificantportionofthewebtobeoffline[6]. Nonetheless, cloud servers dis- persed over multiple regions do not completely solve the problem, as these are
Load more

Recommended publications
  • Evmpatch: Timely and Automated Patching of Ethereum Smart Contracts
    EVMPatch: Timely and Automated Patching of Ethereum Smart Contracts Michael Rodler Wenting Li Ghassan O. Karame University of Duisburg-Essen NEC Laboratories Europe NEC Laboratories Europe Lucas Davi University of Duisburg-Essen Abstract some of these contracts hold, smart contracts have become an appealing target for attacks. Programming errors in smart Recent attacks exploiting errors in smart contract code had contract code can have devastating consequences as an attacker devastating consequences thereby questioning the benefits of can exploit these bugs to steal cryptocurrency or tokens. this technology. It is currently highly challenging to fix er- rors and deploy a patched contract in time. Instant patching is Recently, the blockchain community has witnessed several especially important since smart contracts are always online incidents due smart contract errors [7, 39]. One especially due to the distributed nature of blockchain systems. They also infamous incident is the “TheDAO” reentrancy attack, which manage considerable amounts of assets, which are at risk and resulted in a loss of over 50 million US Dollars worth of often beyond recovery after an attack. Existing solutions to Ether [31]. This led to a highly debated hard-fork of the upgrade smart contracts depend on manual and error-prone pro- Ethereum blockchain. Several proposals demonstrated how to defend against reentrancy vulnerabilities either by means of cesses. This paper presents a framework, called EVMPATCH, to instantly and automatically patch faulty smart contracts. offline analysis at development time or by performing run-time validation [16, 23, 32, 42]. Another infamous incident is the EVMPATCH features a bytecode rewriting engine for the pop- ular Ethereum blockchain, and transparently/automatically parity wallet attack [39].
    [Show full text]
  • ARK​ ​​Whitepaper
    ARK Whitepaper ​ ​​ A Platform for Consumer Adoption ​ ​ ​ ​ ​ ​ ​ ​ v.1.0.3 The ARK Crew ARK Whitepaper v.1.0.3 ​ ​ ​ ​ ​ ​ ​ ​ Table Of Contents ​ ​ ​ ​ Overview………………………………………………………………...……………………………….……………….………………………………………………………….….3 ​ Purpose of this Whitepaper………………………………………………………………………………………………………………………..….……….3 ​ ​ ​ ​ ​ ​ ​ Why?…………………………………………………………………………………………………………………….…………………………………………………….…………..4 ​ ​ ARK…………………………………………………………………………………………………….……………….…………………………………………………………………..5 ​ ​ ARK IS………………………………………………………………………………………………....……………….………………………………………………………………..5 ​ ​ ​ ​ ARK: Technical Details……………………………………….…….…..…………………………...……………….………………...…………………………...6 ​ ​ ​ ​ ​ ​ - Delegated Proof of Stake…………………………….……………...………………………….……………………………………….………...…...6 ​ ​​ ​ ​ ​ ​ ​ ​ ​ - Hierarchical Deterministic (HD) Wallets ​ ​​ ​ ​ ​ ​ ​ ​ (BIP32)…………………………………………………….....…………………..…..8 ​ - Fees……………………………………………………………………………………………………………….……………….…...………………………………..……...8 ​ ​​ ​ - ARK Delegates and Delegate Voting.…………………………………………………………………………………...………………….9 ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ - Bridged Blockchains (SmartBridges)....................………………………………………………………………….………...…….10 ​ ​​ ​ ​ ​ ​ ​ - POST ARK-TEC Token Distribution …………………..…………………………………….………………….………..……..…..……….11 ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ - Testnet Release……………………………………………….…………………………………………………………………….………...….....12 ​ ​ ​ And Beyond?…………………………………………………………………….………...……………………………………….………………………...……….…12 ​ ​ ​ ​ Addendum 1: ARK IS…(Cont.)...……..……..…………....…..………...………………………………………...………………………......……12
    [Show full text]
  • IPFS and Friends: a Qualitative Comparison of Next Generation Peer-To-Peer Data Networks Erik Daniel and Florian Tschorsch
    1 IPFS and Friends: A Qualitative Comparison of Next Generation Peer-to-Peer Data Networks Erik Daniel and Florian Tschorsch Abstract—Decentralized, distributed storage offers a way to types of files [1]. Napster and Gnutella marked the beginning reduce the impact of data silos as often fostered by centralized and were followed by many other P2P networks focusing on cloud storage. While the intentions of this trend are not new, the specialized application areas or novel network structures. For topic gained traction due to technological advancements, most notably blockchain networks. As a consequence, we observe that example, Freenet [2] realizes anonymous storage and retrieval. a new generation of peer-to-peer data networks emerges. In this Chord [3], CAN [4], and Pastry [5] provide protocols to survey paper, we therefore provide a technical overview of the maintain a structured overlay network topology. In particular, next generation data networks. We use select data networks to BitTorrent [6] received a lot of attention from both users and introduce general concepts and to emphasize new developments. the research community. BitTorrent introduced an incentive Specifically, we provide a deeper outline of the Interplanetary File System and a general overview of Swarm, the Hypercore Pro- mechanism to achieve Pareto efficiency, trying to improve tocol, SAFE, Storj, and Arweave. We identify common building network utilization achieving a higher level of robustness. We blocks and provide a qualitative comparison. From the overview, consider networks such as Napster, Gnutella, Freenet, BitTor- we derive future challenges and research goals concerning data rent, and many more as first generation P2P data networks, networks.
    [Show full text]
  • Metamask Pre-Assignment
    MMS 562F: Tech Driven Transformation MetaMask Pre-Assignment Campbell R. Harvey Duke University and NBER February 2021 Setup • Metamask is a cryptocurrency wallet that is used to interface with the Ethereum-based Apps • We will be setting up this Wallet on your mobile device (iOS or Android only) – If you are unable to use a mobile device, the end of this deck has a web browser tutorial (Page 19) – If you already have MetaMask on your browser, the end of this deck has a tutorial to link your Web Account to the Mobile App (Page 25) Campbell R. Harvey 2021 2 Setup • Download the Metamask app from the App Store or Google Play Store • Click Get Started • Click Create a new wallet • Create a new account by typing in a password of your choosing and pressing “Create” • Go through the prompts to secure your wallet • Store Secret Backup Phrase in a secure location, ideally paper or a password manager – not on your phone or computer. • Type in secret backup phrase Campbell R. Harvey 2021 3 1 Using MetaMask 1. Network • This determines which Ethereum Network you are using. Click on this to see all network options in a 2 dropdown. For this class we will only discuss or use the Main Ethereum Network and the Ropsten Test Network. 3 Campbell R. Harvey 2021 4 1 Using MetaMask 1. Network • The Ethereum Mainnet is where live ether (ETH) with real value exists and is 2 used for payment and applications. I will refer to this as the “main network” or the “mainnet” 3 Campbell R.
    [Show full text]
  • A Decentralized Cloud Storage Network Framework
    Storj: A Decentralized Cloud Storage Network Framework Storj Labs, Inc. October 30, 2018 v3.0 https://github.com/storj/whitepaper 2 Copyright © 2018 Storj Labs, Inc. and Subsidiaries This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 license (CC BY-SA 3.0). All product names, logos, and brands used or cited in this document are property of their respective own- ers. All company, product, and service names used herein are for identification purposes only. Use of these names, logos, and brands does not imply endorsement. Contents 0.1 Abstract 6 0.2 Contributors 6 1 Introduction ...................................................7 2 Storj design constraints .......................................9 2.1 Security and privacy 9 2.2 Decentralization 9 2.3 Marketplace and economics 10 2.4 Amazon S3 compatibility 12 2.5 Durability, device failure, and churn 12 2.6 Latency 13 2.7 Bandwidth 14 2.8 Object size 15 2.9 Byzantine fault tolerance 15 2.10 Coordination avoidance 16 3 Framework ................................................... 18 3.1 Framework overview 18 3.2 Storage nodes 19 3.3 Peer-to-peer communication and discovery 19 3.4 Redundancy 19 3.5 Metadata 23 3.6 Encryption 24 3.7 Audits and reputation 25 3.8 Data repair 25 3.9 Payments 26 4 4 Concrete implementation .................................... 27 4.1 Definitions 27 4.2 Peer classes 30 4.3 Storage node 31 4.4 Node identity 32 4.5 Peer-to-peer communication 33 4.6 Node discovery 33 4.7 Redundancy 35 4.8 Structured file storage 36 4.9 Metadata 39 4.10 Satellite 41 4.11 Encryption 42 4.12 Authorization 43 4.13 Audits 44 4.14 Data repair 45 4.15 Storage node reputation 47 4.16 Payments 49 4.17 Bandwidth allocation 50 4.18 Satellite reputation 53 4.19 Garbage collection 53 4.20 Uplink 54 4.21 Quality control and branding 55 5 Walkthroughs ...............................................
    [Show full text]
  • How to Invest in Filecoin
    How to Invest in Filecoin Part I: Preparing to Invest Filecoin investments will be made on CoinList (coinlist.co), a US-based funding platform that connects investors to promising early-stage token sales. Created by Protocol Labs in partnership with AngelList, CoinList simplifies the token sale process and implements robust legal frameworks for token sales in the U.S. Before the sale begins, you will need to complete several preparation steps. Note that some steps include wait time of several days. For this reason, we recommend getting started as soon as possible and working in parallel while waiting for other steps to be reviewed or confirmed. Step 1: Create a CoinList account (5 min) Visit https://coinlist.co. Sign in with your AngelList account, or create a new account if needed. Step 2: Become a US accredited investor through AngelList (30 min + 1-3 day review) All token investors will need to meet US accredited investor requirements. Non-US investors can invest, but must meet the same requirements. You will be prompted to submit accreditation evidence. Step 3: Submit information for KYC/AML checks (15 min + instant review if no issues) You will be prompted to submit the details required for KYC/AML (Know Your Customer/Anti-Money Laundering) checks as soon as accreditation evidence has been submitted. You do not need to wait until accreditation review is complete. Step 4: Transfer funds to relevant accounts (10min + 1-5 day wait) You can invest with your choice of the following currencies: US Dollars, Bitcoin, Ether, and Zcash. To invest using US Dollars: Go to https://coinlist.co/settings/wallet.
    [Show full text]
  • Filecoin Token Sale Economics
    Filecoin Token Sale Economics This document describes various aspects of the Filecoin Network, the Filecoin Token Sale, and the economics of both. Any updates to this document will be posted on the CoinList webpage for the Filecoin Token Sale: https://coinlist.co/currencies/filecoin. LEGAL DISCLAIMER: This document contains forward-looking statements, ​ ​ ​ ​ ​ subject to risks and uncertainties that could cause actual results to differ materially. 1. Token Allocation The Filecoin Token will be distributed to the 4 major participating groups in the Filecoin Network. This allocation is written into the protocol itself and the Filecoin blockchain’s Genesis block. Each group is critical to the network’s creation, development, growth, and maintenance: ● 70% to Filecoin Miners (Mining block reward) ​ For providing data storage service, maintaining the blockchain, distributing data, running contracts, and more. ● 15% to Protocol Labs (Genesis allocation, 6-year linear vesting) ​ For research, engineering, deployment, business development, marketing, distribution, and more. ● 10% to Investors (Genesis allocation, 6 month to 3 year linear vesting) ​ ​ For funding network development, business development, partnerships, support, and more. ● 5% to Filecoin Foundation (Genesis allocation, 6-year linear vesting) ​ ​ For long-term network governance, partner support, academic grants, public works, community building, et cetera. 2. The Filecoin Token Sale Fundraising. Protocol Labs requires significant funding to develop, launch, and grow the Filecoin network. We ​ ​ ​ must develop all the software required: the mining software, the client software, user interfaces and apps, network infrastructure and monitoring, software that third-party wallets and exchanges need to support Filecoin, integrations with other data storage software, tooling for web applications and dapps to use Filecoin, and much more.
    [Show full text]
  • Reputation Driven Dynamic Access Control Framework for Iot Atop Poa Ethereum Blockchain
    Reputation Driven Dynamic Access Control Framework for IoT atop PoA Ethereum Blockchain Auqib Hamid Lonea,∗, Roohie Naaza aDepartment of Computer Science and Engineering., NIT Srinagar, Jammu and Kashmir,India,190006 Abstract Security and Scalability are two major challenges that IoT is currently fac- ing. Access control to critical IoT infrastructure is considered as top security challenge that IoT faces. Data generated by IoT devices may be driving many hard real time systems, thus it is of utmost importance to guarantee integrity and authenticity of the data and resources at the first place itself. Due to heterogeneous and constrained nature of IoT devices, traditional IoT security frameworks are not able to deliver scalable, efficient and manage- able mechanisms to meet the requirements of IoT devices. On the other hand Blockchain technology has shown great potential to bridge the missing gap towards building a truly decentralized, trustworthy, secure and scalable environment for IoT. Allowing access to IoT resources and data managed through Blockchain will provide an additional security layer backed by the strongest cryptographic algorithms available. In this work we present a rep- utation driven dynamic access control framework for IoT applications based on Proof of Authority Blockchain, we name it as Rep-ACM. In Rep-ACM framework we build two major services, one for Reputation building (for bet- ter IoT device behaviour regulations) and other for Misbehaviour detection (for detecting any Misbehaviour on object resource usage). Both of these services work in coordination with other services of proposed framework to determine who can access what and under what conditions access should be granted.
    [Show full text]
  • The Book of Swarm Storage and Communication Infrastructure for Self-Sovereign Digital Society Back-End Stack for the Decentralised Web
    the book of Swarm storage and communication infrastructure for self-sovereign digital society back-end stack for the decentralised web Viktor Trón v1.0 pre-release 7 - worked on November 17, 2020 the swarm is headed toward us Satoshi Nakamoto ii CONTENTS Prolegomena xi Acknowledgments xii i prelude 1 the evolution2 1.1 Historical context 2 1.1.1 Web 1.02 1.1.2 Web 2.03 1.1.3 Peer-to-peer networks 6 1.1.4 The economics of BitTorrent and its limits 7 1.1.5 Towards Web 3.08 1.2 Fair data economy 12 1.2.1 The current state of the data economy 12 1.2.2 The current state and issues of data sovereignty 13 1.2.3 Towards self-sovereign data 15 1.2.4 Artificial intelligence and self-sovereign data 16 1.2.5 Collective information 17 1.3 The vision 18 1.3.1 Values 18 1.3.2 Design principles 19 1.3.3 Objectives 19 1.3.4 Impact areas 20 1.3.5 The future 21 ii design and architecture 2 network 25 2.1 Topology and routing 25 2.1.1 Requirements for underlay network 25 2.1.2 Overlay addressing 26 2.1.3 Kademlia routing 27 2.1.4 Bootstrapping and maintaining Kademlia topology 32 2.2 Swarm storage 35 2.2.1 Distributed immutable store for chunks 35 2.2.2 Content addressed chunks 38 2.2.3 Single-owner chunks 41 2.2.4 Chunk encryption 42 2.2.5 Redundancy by replication 43 2.3 Push and pull: chunk retrieval and syncing 47 iii 2.3.1 Retrieval 47 2.3.2 Push syncing 51 2.3.3 Pull syncing 53 2.3.4 Light nodes 55 3 incentives 57 3.1 Sharing bandwidth 58 3.1.1 Incentives for serving and relaying 58 3.1.2 Pricing protocol for chunk retrieval 59 3.1.3 Incentivising push-syncing
    [Show full text]
  • Exploring the Interconnectedness of Cryptocurrencies Using Correlation Networks
    Exploring the Interconnectedness of Cryptocurrencies using Correlation Networks Andrew Burnie UCL Computer Science Doctoral Student at The Alan Turing Institute [email protected] Conference Paper presented at The Cryptocurrency Research Conference 2018, 24 May 2018, Anglia Ruskin University Lord Ashcroft International Business School Centre for Financial Research, Cambridge, UK. Abstract Correlation networks were used to detect characteristics which, although fixed over time, have an important influence on the evolution of prices over time. Potentially important features were identified using the websites and whitepapers of cryptocurrencies with the largest userbases. These were assessed using two datasets to enhance robustness: one with fourteen cryptocurrencies beginning from 9 November 2017, and a subset with nine cryptocurrencies starting 9 September 2016, both ending 6 March 2018. Separately analysing the subset of cryptocurrencies raised the number of data points from 115 to 537, and improved robustness to changes in relationships over time. Excluding USD Tether, the results showed a positive association between different cryptocurrencies that was statistically significant. Robust, strong positive associations were observed for six cryptocurrencies where one was a fork of the other; Bitcoin / Bitcoin Cash was an exception. There was evidence for the existence of a group of cryptocurrencies particularly associated with Cardano, and a separate group correlated with Ethereum. The data was not consistent with a token’s functionality or creation mechanism being the dominant determinants of the evolution of prices over time but did suggest that factors other than speculation contributed to the price. Keywords: Correlation Networks; Interconnectedness; Contagion; Speculation 1 1. Introduction The year 2017 saw the start of a rapid diversification in cryptocurrencies.
    [Show full text]
  • An Architecture for Client Virtualization: a Case Study
    Computer Networks 100 (2016) 75–89 Contents lists available at ScienceDirect Computer Networks journal homepage: www.elsevier.com/locate/comnet An architecture for client virtualization: A case study ∗ Syed Arefinul Haque a, Salekul Islam a, , Md. Jahidul Islam a, Jean-Charles Grégoire b a United International University, Dhaka, Bangladesh b INRS-EMT, Montréal, Canada a r t i c l e i n f o a b s t r a c t Article history: As edge clouds become more widespread, it is important to study their impact on tradi- Received 30 November 2015 tional application architectures, most importantly the separation of the data and control Revised 17 February 2016 planes of traditional clients. We explore such impact using the virtualization of a Peer- Accepted 18 February 2016 to-Peer (P2P) client as a case study. In this model, an end user accesses and controls the Available online 26 February 2016 virtual P2P client application using a web browser and all P2P application-related control Keywords: messages originate and terminate from the virtual P2P client deployed inside the remote Edge cloud server. The web browser running on the user device only manages download and upload of P2P the P2P data packets. BitTorrent, as it is the most widely deployed P2P platform, is used to BitTorrent validate the feasibility and study the performance of our approach. We introduce a proto- Virtual client type that has been deployed in public cloud infrastructures. We present simulation results Cloud-based server which show clear improvements in the use of user resources. Based on this experience we Web-RTC derive lessons on the challenges and benefits from such edge cloud-based deployments.
    [Show full text]
  • A Privacy-Preserving Decentralized Storage with Payments Based on a Blockchain
    A Privacy-preserving Decentralized Storage with Payments Based on a Blockchain Dissertation zur Erlangung des Doktorgrades Dr. rer. nat. der Fakultat¨ fur¨ Ingenieurwissenschaften, Informatik und Psychologie der Universitat¨ Ulm Henning Johannes Gustav Kopp aus Villingen-Schwenningen 2018 Institut f¨urVerteilte Systeme Universit¨atUlm, Deutschland Amtierender Dekan: Prof. Maurits Ortmanns Gutachter: Prof. Frank Kargl Gutachter: Prof. Frederik Armknecht Tag der Promotion: 20.12.2018 Summary Recently, the paradigm of cloud storage has seen wide acceptance in industry and for personal use. One of its core principles is to outsource storage, such that users can be billed flexibly by their actual demand. However, outsourcing storage such as private data or business secrets leads to privacy problems, as control over the data is lost to the storage provider. This is intensified by the fact that often privacy is considered only as an afterthought in these systems and not integrated into the design from the beginning. Privacy-preserving alternatives to these centralized cloud storage providers are peer-to-peer systems like Freenet or GNUnet. In these systems, participants can donate storage to other users of the system. Privacy plays a vital role in these systems, as, e. g., participants are unable to access data of other users if they are not authorized to do so, even if the data of the other users resides on their own hard disk. However, these decentralized systems suffer from limited contribution due to a lack of incentives to participate. Naively enhancing these systems with the possibility of payments such that storage providers can earn money, infringes privacy, since tracing of payment flows provides links between users and their storage providers.
    [Show full text]