PaperlayerView exact revision on arXiv

Source-linked AI summary

A Survey on Security and Privacy Issues of Bitcoin

Mauro Conti, Sandeep Kumar E, Chhagan Lal, Sushmita Ruj

arXiv:1706.00916v3cs.CR

TL;DR

Bitcoin’s growing adoption and value expose weaknesses in its consensus, network, security, and privacy mechanisms. This paper systematically surveys Bitcoin’s architecture, threats, countermeasures, privacy solutions, and open challenges. It concludes that double spending remains possible, transparency undermines privacy, and scalability and incentives remain unresolved concerns.

  • Problem

    Bitcoin’s valuable, widely used system faces security threats and privacy challenges across its blockchain, consensus protocol, network, exchanges, and user environment.

  • Method

    The paper conducts a comprehensive survey of Bitcoin’s components, security and privacy threats, proposed countermeasures, privacy-preserving solutions, and future research directions.

  • Results

    The survey finds that double spending cannot be completely prevented by existing solutions, Bitcoin’s transparency creates a global attacker model, and 51% attacks remain a major issue.

  • Takeaways & Limitations

    Bitcoin’s security depends on distributed mining and fast network propagation, while its transparency means the system is anything but private.

  • Takeaways & Limitations

    Bitcoin’s protocol restricts the network to about 7 transactions per second because block sizes are limited to 1MB.

Abstract

from arXiv · show

Bitcoin is a popular cryptocurrency that records alltransactions in a distributed append-only public ledger calledblockchain. The security of Bitcoin heavily relies on the incentive-compatible proof-of-work (PoW) based distributed consensus pro-tocol, which is run by network nodes called miners. In exchangefor the incentive, the miners are expected to honestly maintainthe blockchain. Since its launch in 2009, Bitcoin economy hasgrown at an enormous rate, and it is now worth about 170 billions of dollars. This exponential growth in the market valueof Bitcoin motivates adversaries to exploit weaknesses for profit,and researchers to discover new vulnerabilities in the system,propose countermeasures, and predict upcoming trends.In this paper, we present a systematic survey that covers thesecurity and privacy aspects of Bitcoin. We start by presenting anoverview of the Bitcoin protocol and its major components alongwith their functionality and interactions within the system. Wereview the existing vulnerabilities in Bitcoin and its underlyingmajor technologies such as blockchain and PoW based consensusprotocol. These vulnerabilities lead to the execution of varioussecurity threats to the normal functionality of Bitcoin. Wethen discuss the feasibility and robustness of the state-of-the-art security solutions. Additionally, we present current privacyand anonymity considerations in Bitcoin and discuss the privacy-related threats to Bitcoin users along with the analysis of theexisting privacy-preserving solutions. Finally, we summarize thecritical open challenges and suggest directions for future researchtowards provisioning stringent security and privacy techniquesfor Bitcoin.

I. INTRODUCTION

Bitcoin is a decentralized, open-source electronic payment system whose growing value and adoption have exposed security and privacy challenges. This survey reviews Bitcoin’s architecture, threats, countermeasures, privacy concerns, open issues, and future research directions.

  • Bitcoin background: Bitcoin uses peer-to-peer technology without a trusted centralized authority, giving owners direct control over their bitcoins.Its design is open-source and operates without banks, notaries, or other centralized services.
  • Bitcoin background: Bitcoin provides a cryptographically secure electronic payment system using digital tokens called bitcoins.
  • Motivation: 170 billion dollars in market capitalization and more than 375,000 confirmed daily transactions made Bitcoin a major target for adversaries by December 2017.Reported attacks included double spending, netsplits, transaction malleability, networking attacks, and mining-related attacks.
  • Survey scope: The survey presents Bitcoin’s components, functionalities, and interactions, including transactions, blockchain, consensus protocols, and mining.
  • Survey scope: The authors systematically examine practical and theoretical security and privacy threats across Bitcoin’s operation.The survey covers threats affecting Bitcoin directly or through underlying technologies.
  • Survey contributions: The survey evaluates the efficiency and limitations of state-of-the-art countermeasures and privacy-enhancing solutions, then identifies lessons, open issues, and future directions.It aims to help readers understand threat scope, estimate potential damage, and identify directions for threat detection and containment.

A. Transaction and Proof-of-Work

Bitcoin transactions are assembled into blocks, validated through proof-of-work, and appended to a distributed blockchain. This process supports transaction integrity but remains exposed to forks, double spending, and mining-related attacks.

  • Transactions: Transactions contain inputs referencing previous outputs and outputs specifying transferred coins and the new owner’s Bitcoin address.Transaction scripts define the conditions for claiming coins; P2PKH commonly requires one owner signature, while P2SH supports multisignature addresses and other transaction types.
  • Proof-of-Work: Miners bundle pending transactions into blocks, solve a SHA-256 proof-of-work puzzle by varying a nonce, and broadcast valid blocks for network verification.The block hash must be at or below a shared 256-bit target value.
  • Mining Incentives: Mining rewards and transaction fees incentivize miners to validate blocks and add them to the public append-only blockchain.The block reward is created through a coinbase transaction, while the transaction fee is the difference between total inputs and outputs.
  • Proof-of-Work: The proof-of-work target is adjusted every 2,016 blocks according to the network’s actual block-generation time.The adjustment uses the previous target and the time taken to generate the last 2,016 blocks.
  • Blockchain Forks: Network latency or simultaneous valid solutions can create equal-length blockchain forks, after which miners extend the longer chain.A malicious miner can privately mine a competing chain and publish it when it becomes longer, potentially disturbing normal operation or gaining profits.
  • Security Assumptions: Bitcoin security assumes that honest miners control most computing resources, but a miner controlling 51% of hashing power can write blocks or fork the chain.The resulting behavior can support double spending, eclipse, and denial-of-service attacks.

C. Consensus Protocol

Bitcoin uses proof-of-work consensus to coordinate independently operating nodes without a trusted third party. The model scales to many participants but faces security, performance, scalability, latency, and energy-consumption challenges.

  • Consensus Model: Bitcoin nodes collaboratively construct the blockchain and use consensus to agree on the order in which entries are appended.The protocol is designed to tolerate crashed, malicious, or disconnected nodes without relying on a central authority.
  • Consensus Model: Proof-of-work consensus allows participants to join without authentication, supporting scalability across thousands of network nodes.Its security depends on the assumption that honest players control a majority of computing resources.
  • Consensus Threats: A 51% attack lets an adversary control enough mining power to write blocks or fork the blockchain, enabling double spending, eclipse, and denial-of-service attacks.Attackers may also incentivize or bribe honest miners to join their coalition.
  • Performance and Scalability: Network latency increases temporary forks and transaction confirmation times, while Bitcoin’s 1MB block-size limit restricts sustained throughput to 7 transactions per second.The paper contrasts this rate with the millions of transactions per second reported for MasterCard or VISA.
  • Performance and Scalability: Proof-of-work consumes substantial computational energy and has been criticized for inefficient power consumption and block-generation time.Alternative consensus protocols discussed include Proof-of-Stake, Proof of Elapsed Time, Proof of Authority, PBFT, and FBFT.

D. Networking Infrastructure

Bitcoin’s networking infrastructure uses an unstructured peer-to-peer overlay to rapidly propagate transactions and blocks, but propagation delays and inconsistent blockchain views can threaten consensus and enable attacks.

  • Networking architecture: Bitcoin uses unstructured P2P networking over persistent TCP connections, with peers maintaining potential-neighbor address lists and typically at least eight connections.Peers exchange addresses through DNS bootstrapping and neighbor communication; connections remain active through periodic hello messages.
  • Propagation mechanisms: Transactions propagate through INV, GETDATA, and TX messages, while miners request newly announced blocks with GETDATA and receive them in BLOCK messages.This message sequence lets nodes announce, request, and share transactions and blocks that have not yet entered the blockchain.
  • Security implications: Flooding newly discovered transactions and blocks supports distributed consensus, but adversaries can delay propagation to launch double-spend and netsplit attacks or waste mining power.Propagation delays can isolate network regions, extend transaction and block delivery times, and disrupt mining efficiency.
  • Security implications: Bitcoin’s consensus security depends on a globally consistent blockchain state, which propagation variations can undermine and thereby enable successful double spending.The rapid distribution enabled by the P2P network is therefore tightly coupled to PoW-based consensus security.
  • Broader challenges: The networking model retains open scalability and decentralization challenges, while Bitcoin also faces risks involving energy use, lost wallets, criminal activity, and economic, legal, social, and technological factors.The paper notes that PoW consumes substantial energy, lost private keys can permanently strand coins, and anonymity can facilitate illicit activity.

III. SECURITY: ATTACKS ON BITCOIN SYSTEMS

Bitcoin’s attack surface spans wallets, networks, transactions, exchanges, and mining, with double spending arising when conflicting transactions and competing blockchain forks are accepted in the required sequence.

  • Threat landscape: Bitcoin security threats include double spending, wallet attacks, network attacks such as DDoS, Sybil, and eclipse attacks, and mining attacks such as 50%, withholding, and bribery attacks.The survey organizes these threats by affected Bitcoin components and discusses their impacts and proposed solutions.
  • Double spending: A double spend occurs when a client rapidly sends two conflicting transactions that use the same bitcoins in different transactions.The network normally identifies conflicting inputs during propagation and mining, processes one transaction, and rejects the other.
  • Double spending: A successful double spend requires one part of the network to confirm the vendor transaction, another part to accept the conflicting transaction, a resulting fork, and majority-miner support for the attacker’s chain.If these events occur in sequence, the attacker obtains the product while the conflicting transaction later becomes valid on the longer chain.
  • Double-spend variants: Finney attacks use a privately pre-mined block to invalidate a vendor transaction after the vendor releases goods, but they require a one-confirmation vendor.Multiple confirmations make the attack harder, although the possibility of double spending remains.
  • Double-spend variants: Brute-force attacks extend the private chain until it exceeds a vendor’s x confirmations, after which miners adopt the longer chain and produce the same effects as a Finney attack.The attacker needs sufficient resources to privately mine x blocks ahead of the public chain.
  • Double-spend variants: Vector 76 attacks exploit exchanges by invalidating a deposited transaction after the attacker withdraws the same coins, causing the exchange to lose funds.The attack depends on competing forks: the deposit-containing fork must be replaced after the withdrawal is completed.
  • Mining power and systemic risk: Higher miner computing power increases double-spend success probability, while a miner controlling more than 50% of network resources can double spend, manipulate transactions, and destabilize the network.The survey identifies mining rate, propagation delay, vendors, clients, and exchanges as additional factors affecting attack success.

B. Mining Pool Attacks

Mining pools create concentrated incentives and attack surfaces, including strategies that withhold blocks, manipulate rewards, sabotage competitors, or censor transactions. Several attacks exploit pool coordination and can remain difficult to detect or require substantial hash power.

  • Pool operation: Mining pools aggregate computing power through managers who assign work and use submitted shares to measure members’ contributions.A share is a low-difficulty proof whose expected frequency is proportional to the hashes computed by a miner.
  • Attack surface: Mining-pool attacks include internal reward manipulation and disruption, while external attackers can exploit greater hash power for attacks such as double spending.The survey frames these as vulnerabilities arising from pool-based mining.
  • Block withholding: Selfish mining withholds blocks and selectively reveals them, allowing an attacker to increase reward and waste honest miners’ resources.The attack strengthens as honest miners are lured toward selfish pools; a sufficiently large pool might approach a > 50% attack.
  • Block withholding: Block withholding sabotages a pool by submitting partial proofs-of-work while withholding full blocks, reducing the pool’s revenue.The described scenarios include sabotage and lie-in-wait strategies.
  • Pool incentives: Pool hopping uses submitted-share information to switch pools or mine independently when expected rewards become less favorable.An adversary monitors shares and may leave after many shares have accumulated without a discovered block.
  • Transaction censorship: Punitive forking requires > 50% hashrate for selective blacklisting, whereas feather forking can block transactions with less than 50% hash power but may lose rewards.Other miners may also participate to avoid losses, and feather forking can support blackmail threats.

C. Client-side Security Threats

Client-side security threats center on protecting cryptographic keys and wallet holdings. The survey reviews wallet risks and exchange-based safeguards, including privacy-preserving proofs that exchanges control sufficient customer funds.

  • Key management: Bitcoin users face immediate and irrevocable monetary losses when private keys are lost or compromised.This makes secure yet usable key-management techniques especially important.
  • Transaction security: Bitcoin uses ECDSA and related cryptographic mechanisms to authenticate transactions and prove ownership of funds.In P2PKH transactions, users provide a public key and a signature generated with the private key.
  • Wallets: Wallet implementations include software, online or hosted, hardware or offline, paper, and brain wallets.These designs address the secure storage and management of user keys.
  • Exchange risk: Online exchanges reduce some wallet-management burdens but expose users to exchange failures, theft, technical mistakes, and bankruptcy.The survey cites Mt. Gox as a major exchange failure that lost over 450 million dollars.
  • Exchange safeguards: Provisions is a privacy-preserving proof of solvency requiring exchanges to periodically demonstrate control of enough bitcoins to settle customer accounts.The mechanism is presented as a safeguard rather than a complete elimination of exchange vulnerability.

D. Bitcoin Network Attacks

Bitcoin’s network and protocol implementations expose exchanges, pools, wallets, and users to attacks involving denial of service, routing, timing, malleability, refunds, and isolation. The survey summarizes attack mechanisms, demonstrated impacts, and proposed or required mitigations.

  • DDoS attacks: Game-theoretic analyses compare constructive capacity investment with destructive DDoS attacks that reduce competing mining pools’ expected success.Continuous DDoS attacks forced CoinWallet and BitQuick to shut down after only a few months.
  • Network isolation: Network partitioning and eclipse attacks isolate honest nodes or a specific miner by blocking, diverting, or spoofing peer connections.Eclipse attackers can support N-confirmation double spending and selfish mining with helper nodes.
  • Malleability: Transaction malleability creates a syntactically different but semantically equivalent transaction, potentially enabling exchange double spending.The problem arises when exchanges identify success only by the original transaction ID instead of semantic equivalence.
  • Malleability: Mt. Gox’s vulnerable workflow credited funds after failing to find the original transaction ID, allowing a customer to withdraw coins twice.The correct check would search for any transaction semantically equivalent to the original.
  • Routing attacks: Routing attacks are practical because Bitcoin combines easy routing manipulation with increasing centralization of mining power and routing.The cited study examines both small- and large-scale attacks.
  • Payment protocols: Refund attacks exploit vulnerabilities in BIP70 payment refunds, while temporary mitigations do not fully resolve the issues without revising the standard.Coinbase and BitPay acknowledged the attacks and applied temporary measures.
  • Timing attacks: Time jacking manipulates a node’s network-time estimate through fake peers reporting inaccurate timestamps.An advanced attack can speed miners’ clocks while slowing a target’s clock, with skew bounded by 70 minutes per node.

E. Practical attack incidents on Bitcoin

Bitcoin attacks have affected exchanges, marketplaces, wallets, and related technologies, with losses sometimes severe but attribution occasionally uncertain. The incidents underscore security weaknesses in cryptocurrency marketplaces and exchanges as bitcoin holdings and values rise.

  • 744,408 bitcoins were lost in the Mt. Gox incident, which contributed to the exchange’s shutdown and a three-month low in bitcoin value.The passage says the legitimacy of the attack was not completely confirmed.
  • Silk Road reported a powerful distributed denial-of-service attack and attributed repeated withdrawals to Bitcoin transaction malleability.The passage states that transaction malleability is being addressed by SegWit, while the principal issue appeared to be human rather than protocol-level.
  • Bitstamp lost about $5 million through phishing targeting personnel, but limited hot-wallet exposure allowed it to cover the theft without direct customer losses.
  • Poloniex lost 12.3% of its bitcoins after an attacker repeatedly clicked withdrawal.
  • The incidents indicate that security is a vital concern and major weakness for cryptocurrency marketplaces and exchanges as bitcoin holdings and values increase.The passage also identifies digital wallets as increasingly attractive targets for hackers.

IV. SECURITY: COUNTERMEASURES FOR BITCOIN ATTACKS

This section presents state-of-the-art security solutions as possible countermeasures for attacks against Bitcoin and its underlying technologies.

  • The section discusses possible countermeasures for the array of attacks affecting Bitcoin and its underlying technologies.

A. No more double spending

Bitcoin countermeasures address double spending through PoW, monitoring, confirmation delays, detection techniques, deposits, and mining-pool defenses. However, no existing solution guarantees complete protection, leaving merchants to trade transaction risk against delivery time.

  • Proof-of-work helps resist double spending by limiting adversarial computational resources and relying on honest miners to synchronize blockchain history.
  • Waiting for more confirmations reduces the possibility of a successful double spend but increases the time before goods or services are delivered.Each new block added above a transaction generates a confirmation.
  • Fast-payment detection techniques include listening periods, controlled observers, and forwarding double-spending attempts to vendors.Observers relay more transactions to the vendor, increasing opportunities to detect a double spend before product release.
  • 2P-PoW is proposed to prevent large mining pools after GHash.IO briefly reached 54% hash power, exceeding the theoretical 51% threshold.
  • Fair deposits and safety deposits penalize double spenders and can compensate victims, while non-equivocation contracts remain vulnerable to payer-beneficiary collusion.
  • No literature solution guarantees complete protection from double spending, so merchants must balance confirmation-related delivery time against attack risk.Adversaries likewise weigh computing-resource and pre-mined-block losses if an attack fails.

B. Countermeasures for Private Forking and Pool Attacks

Countermeasures for private forking and pool attacks target selfish mining, block withholding, bribery, and related incentive manipulation. Proposed designs alter fork selection, block publication, timestamps, or miner incentives.

  • Countermeasures for Private Forking and Pool Attacks: Private forks enable selfish mining, block discarding, block withholding, and bribery attacks that seek to manipulate Bitcoin’s mining incentives.
  • Countermeasures for Private Forking and Pool Attacks: Freshness Preferred uses unforgeable block timestamps and random beacons to favor recent blocks and prevent miners from using future timestamps.
  • Countermeasures for Private Forking and Pool Attacks: Publishing intermediate blocks and selecting the branch with the greatest total work are proposed defenses against selfish mining.The intermediate blocks are valid at lower puzzle difficulty but provide no mining reward.
  • Countermeasures for Private Forking and Pool Attacks: ZeroBlock rejects a privately held block published after a specified interval, requiring consecutive blocks to reach honest miners promptly.
  • Countermeasures for Private Forking and Pool Attacks: Anti-payment counter-bribing offers pool miners more value than an attacker’s payment, but the approach has drawbacks for legitimate pool managers.

C. Securing Bitcoin wallets

Bitcoin wallet security combines encrypted private-key storage, offline cold wallets, and multi-signature control, but stronger control can reduce privacy and anonymity.

  • Wallets store each account’s private key under a randomly generated master key encrypted with AES-256-CBC using a passphrase-derived key.The derivation uses SHA-512 and OpenSSL’s EVP BytesToKey.
  • Cold wallets isolate excess funds on a private-key-enabled computer disconnected from the Internet.The method generates a new private key offline and transfers excess funds to that wallet.
  • Multi-signature transactions split spending control across multiple keys to strengthen wallet security.BitGo is described as providing 2-of-3 multi-signature transactions.
  • Multi-signature transactions can greatly compromise user privacy and anonymity.

1) DDoS Attacks:

The surveyed countermeasures address denial-of-service and related network threats through game-theoretic analysis, alternative consensus designs, monitoring, trusted-peer controls, and faster propagation. These approaches improve resilience, but network security remains dependent on maintaining enough honest miners and adequate incentives.

  • DDoS Attacks: Game-theoretic analysis models competing mining pools and concludes that larger pools can impose DDoS attacks on smaller pools.The pools compete by increasing computational costs over one another.
  • DDoS Attacks: Proof-of-Activity is proposed as robust against DDoS attacks that broadcast many invalid blocks.The protocol stores a cryptographic value in each block header and uses honest stakeholders to validate subsequent transaction storage.
  • DDoS Attacks: Continuous traffic monitoring with SVM and clustering can identify and isolate misbehaving network regions.
  • DDoS Attacks: Time-jacking defenses replace network time with system time, tighten timestamp windows, and use trusted peers.Multiple timestamps and blockchain-dependent timestamps are also suggested.
  • DDoS Attacks: Eclipse-attack countermeasures store trustworthy peer addresses, apply trust thresholds, and use intrusion detection for misbehaving nodes.
  • DDoS Attacks: Offline micropayments can reduce validation delay and network load while allowing parties to transact without revealing identities to routing nodes.The described channel supports high-speed payments, indefinite operation, multiple keys, and third-party-independent validation.
  • DDoS Attacks: Accelerating transaction propagation with proximity-based peer selection is proposed to reduce successful double-spending probability.The Bitcoin Clustering Based Ping Time protocol uses information such as ping latency when connecting to peers.
  • DDoS Attacks: Security and consensus efficiency depend on the number of honest miners, while rewards halving every four years may encourage migration to better-paying cryptocurrencies.

V. PRIVACY AND ANONYMITY IN BITCOIN

Bitcoin provides pseudonymity rather than complete anonymity: public transaction and network data can be analyzed to link addresses, transactions, and users. The survey describes graph-based clustering and deanonymization techniques that expose these links, including IP-to-key inference and online purchase tracking.

  • Bitcoin’s public blockchain reveals transaction data, while pseudonymous keys provide only partial unlinkability.New key pairs reduce linkability, but multi-input transactions reveal common ownership and later identification can expose related transactions.
  • Blockchain Analysis and Deanonymization: Transaction graphs represent bitcoin flows between transactions, with edge weights capturing input and output amounts and timestamps.
  • Blockchain Analysis and Deanonymization: Address graphs are derived from transaction graphs to represent relationships between Bitcoin addresses.
  • Blockchain Analysis and Deanonymization: Entity graphs group addresses that heuristics indicate belong to the same user and connect those user clusters.The grouping uses the address graph and Bitcoin-protocol-derived heuristics.
  • Blockchain Analysis and Deanonymization: Input co-ownership and change-address heuristics enable address clustering and transaction linkability.The first heuristic assumes transaction inputs generally come from one user; transitive closure then expands address clusters.
  • Blockchain Analysis and Deanonymization: Cluster identities can be linked with high precision to online wallets, vendors, and service providers, while regular-user identification is more difficult.Authorities with subpoena power may identify individuals through centralized servers’ customer records.
  • Blockchain Analysis and Deanonymization: Third-party trackers can uniquely identify cryptocurrency purchases on the blockchain and link them to cookies, real identities, and purchase histories.
  • Blockchain Analysis and Deanonymization: Supernode observation can link Bitcoin public keys to IP addresses with nearly 30% accuracy by exploiting transaction-diffusion patterns.The approach requires minimal knowledge of the peer-to-peer graph and may support higher accuracy with more sophisticated traffic analysis.

B. Proposals for enabling privacy and improving anonymity

Bitcoin’s initial design does not make privacy inherent, and public-chain analysis creates privacy and fungibility risks. The surveyed privacy-enhancing proposals include mixing protocols that seek to break links between users and their coins.

  • Privacy weaknesses in Bitcoin have motivated privacy-enhancing technologies intended to strengthen privacy and anonymity without changing fundamental design principles.
  • The public blockchain allows funds to be tracked and tainted, placing the fungibility of individual coins at risk.
  • Mixers divide funds into smaller parts, combine them with other clients’ parts, and produce new coins to break links between users and purchased coins.Mixers are external services rather than an integral part of Bitcoin.
  • CoinJoin joins multiple transactions into one while preserving their inputs and outputs, aiming to improve privacy and prevent theft.The survey presents it among peer-to-peer mixing protocols evaluated for anonymity and transaction security.

2) Distributed mixing networks:

The survey presents mixing and cryptographic techniques as approaches to improve Bitcoin transaction privacy, while emphasizing trade-offs and unresolved scalability, security, and privacy challenges.

  • Distributed mixing networks: MixCoin uses a third-party currency mix to return coins from another user, providing strong anonymity from external entities.Its protocol uses standard-sized transactions and reputation-based cryptography.
  • Distributed mixing networks: TumbleBit enables fast, off-blockchain anonymous payments through an untrusted intermediary that cannot link senders to receivers.Mixing payments from 800 users is reported to provide strong anonymity, theft resistance, and scalability.
  • Bitcoin extensions or Altcoins: Zerocoin uses zero-knowledge proofs to prevent transaction-graph analysis, but requires protocol modifications and substantially increases computational complexity and blockchain size.Its anonymity and counterfeiting resistance depend on strong cryptographic assumptions.
  • Privacy and anonymity: Bitcoin is pseudo-anonymous because accounts are tied to random, multiple addresses rather than directly to individual users.The survey argues that increasing adoption heightens the need for stronger privacy, security, and anonymity protection.
  • Privacy and anonymity: Bitcoin’s transparent ledger supports verification but exposes transactions to a ubiquitous global attacker model, making the system anything but private.Commitment schemes such as zero-knowledge proofs can improve transaction unlinkability and untraceability.
  • Future research directions: Scalability, propagation delay, declining mining rewards, transaction fees, and security and privacy threats remain pressing open issues.The survey notes that it remains unclear which alternative approaches will produce practical improvements.

VII. CONCLUSIONS

The survey concludes that Bitcoin’s popularity and proof-of-work-based protections coexist with unresolved security threats and privacy shortcomings. It emphasizes open research directions for stronger security, privacy, and anonymity.

  • Conclusions: Bitcoin’s popularity and large market capitalization continue to attract adversaries seeking to exploit security weaknesses.The survey reports approximately 1,146 cryptocurrencies and identifies attacks ranging from packet sniffing to double spending.
  • Conclusions: Proof-of-work and consensus robustly protect user actions, yet they can themselves become targets for cyber thieves.The survey states that effective security solutions ensuring Bitcoin’s future functioning remain absent for some attacks.
  • Conclusions: The paper highlights unresolved privacy and anonymity problems and proposes future research directions to motivate further work on Bitcoin systems.Its stated focus includes user privacy and anonymity in the rapidly growing e-commerce context.
Loading 1706.00916v3…