Skip to main navigation Skip to search Skip to main content

Brief Announcement: How to Tame Multiple Spending in Decentralized Cryptocurrencies

  • Institut Polytechnique de Paris

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

The last decade has seen a variety of Asset-Transfer systems designed for decentralized environments. To address the problem of double-spending, these systems inherently make strong model assumptions and spend a lot of resources. In this paper, we take a non-orthodox approach to the double-spending problem that might suit better realistic environments in which these systems are to be deployed. We consider the decentralized trust setting, where each user may independently choose who to trust by forming its local quorums. In this setting, we define k-Spending Asset Transfer, a relaxed version of asset transfer which bounds the number of times the same asset can be spent. We establish a precise relationship between the decentralized trust assumptions and k, the optimal spending number of the system.

Original languageEnglish
Title of host publicationPODC 2022 - Proceedings of the 2022 ACM Symposium on Principles of Distributed Computing
PublisherAssociation for Computing Machinery
Pages427-429
Number of pages3
ISBN (Electronic)9781450392624
DOIs
Publication statusPublished - 20 Jul 2022
Event41st ACM Symposium on Principles of Distributed Computing, PODC 2022 - Salerno, Italy
Duration: 25 Jul 202229 Jul 2022

Publication series

NameProceedings of the Annual ACM Symposium on Principles of Distributed Computing

Conference

Conference41st ACM Symposium on Principles of Distributed Computing, PODC 2022
Country/TerritoryItaly
CitySalerno
Period25/07/2229/07/22

Keywords

  • accountability
  • asset transfer
  • consistency measure
  • decentralized trust
  • quorum systems

Fingerprint

Dive into the research topics of 'Brief Announcement: How to Tame Multiple Spending in Decentralized Cryptocurrencies'. Together they form a unique fingerprint.

Cite this