https://blog.trailofbits.com/2022/06/21/are-blockchains-decentralized/ Trail of Bits Blog Menu Skip to content * Home Are blockchains decentralized? * Post * June 21, 2022 * Leave a comment A new Trail of Bits research report examines unintended centralities in distributed ledgers Blockchains can help push the boundaries of current technology in useful ways. However, to make good risk decisions involving exciting and innovative technologies, people need demonstrable facts that are arrived at through reproducible methods and open data. We believe the risks inherent in blockchains and cryptocurrencies have been poorly described and are often ignored--or even mocked--by those seeking to cash in on this decade's gold rush. In response to recent market turmoil and plummeting prices, proponents of cryptocurrency point to the technology's fundamentals as sound. Are they? * Read the report * Listen to our podcast about this report * Follow along on Twitter Over the past year, Trail of Bits was engaged by the Defense Advanced Research Projects Agency (DARPA) to examine the fundamental properties of blockchains and the cybersecurity risks associated with them. DARPA wanted to understand those security assumptions and determine to what degree blockchains are actually decentralized. To answer DARPA's question, Trail of Bits researchers performed analyses and meta-analyses of prior academic work and of real-world findings that had never before been aggregated, updating prior research with new data in some cases. They also did novel work, building new tools and pursuing original research. The resulting report is a 30-thousand-foot view of what's currently known about blockchain technology. Whether these findings affect financial markets is out of the scope of the report: our work at Trail of Bits is entirely about understanding and mitigating security risk. The report also contains links to the substantial supporting and analytical materials. Our findings are reproducible, and our research is open-source and freely distributable. So you can dig in for yourself. Key findings * Blockchain immutability can be broken not by exploiting cryptographic vulnerabilities, but instead by subverting the properties of a blockchain's implementations, networking, and consensus protocols. We show that a subset of participants can garner undue, centralized control over the entire system: + While the encryption used within cryptocurrencies is for all intents and purposes secure, it does not guarantee security, as touted by proponents. + Bitcoin traffic is unencrypted; any third party on the network route between nodes (e.g., internet service providers, Wi-Fi access point operators, or governments) can observe and choose to drop any messages they wish. + Tor is now the largest network provider in Bitcoin; just about 55% of Bitcoin nodes were addressable only via Tor (as of March 2022). A malicious Tor exit node can modify or drop traffic. * More than one in five Bitcoin nodes are running an old version of the Bitcoin core client that is known to be vulnerable. * The number of entities sufficient to disrupt a blockchain is relatively low: four for Bitcoin, two for Ethereum, and less than a dozen for most proof-of-stake networks. * When nodes have an out-of-date or incorrect view of the network, this lowers the percentage of the hashrate necessary to execute a standard 51% attack. During the first half of 2021, the actual cost of a 51% attack on Bitcoin was closer to 49% of the hashrate--and this can be lowered substantially through network delays. * For a blockchain to be optimally distributed, there must be a so-called Sybil cost. There is currently no known way to implement Sybil costs in a permissionless blockchain like Bitcoin or Ethereum without employing a centralized trusted third party (TTP). Until a mechanism for enforcing Sybil costs without a TTP is discovered, it will be almost impossible for permissionless blockchains to achieve satisfactory decentralization. Novel research within the report * Analysis of the Bitcoin consensus network and network topology * Updated analysis of the effect of software delays on the hashrate required to exploit blockchains (we did not devise the theory, but we applied it to the latest data) * Calculation of the Nakamoto coefficient for proof-of-stake blockchains (once again, the theory was already known, but we applied it to the latest data) * Analysis of software centrality * Analysis of Ethereum smart contract similarity * Analysis of mining pool protocols, software, and authentication * Combining the survey of sources (both academic and anecdotal) that support our thesis that there is a lack of decentralization in blockchains The research to which this blog post refers was conducted by Trail of Bits based upon work supported by DARPA under Contract No. HR001120C0084 (Distribution Statement A, Approved for Public Release: Distribution Unlimited). Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the United States Government or DARPA. Share this: * Twitter * LinkedIn * Reddit * Telegram * Facebook * Pocket * Email * Print * Like this: Like Loading... By Trail of Bits Posted in DARPA, Press Release, Research Practice Post navigation - Announcing the new Trail of Bits podcast Leave a Reply Cancel reply Search [ ] [Search] About Us Since 2012, Trail of Bits has helped secure some of the world's most targeted organizations and products. We combine high-end security research with a real world attacker mentality to reduce risk and fortify code. Read more at www.trailofbits.com Subscribe via RSS RSS feed RSS - Posts Recent Posts * Are blockchains decentralized? * Announcing the new Trail of Bits podcast * Themes from PyCon US 2022 * Interactive decompilation with rellic-xref * Themes from Real World Crypto 2022 * Improving the state of go-fuzz * Amarna: Static analysis for Cairo programs * The Frozen Heart vulnerability in PlonK * The Frozen Heart vulnerability in Bulletproofs * The Frozen Heart vulnerability in Girault's proof of knowledge * Coordinated disclosure of vulnerabilities affecting Girault, Bulletproofs, and PlonK * Towards Practical Security Optimizations for Binaries * Optimizing a smart contract fuzzer * Maat: Symbolic execution made easy * Part 2: Improving crypto code in Rust using LLVM's optnone Yearly Archive * 2020 * 2019 * 2018 * 2017 * 2016 * 2015 * 2014 * 2013 * 2012 Categories * Apple (13) * Attacks (9) * Audits (1) * Authentication (5) * Binary Ninja (12) * Blockchain (46) * Capture the Flag (11) * CodeQL (2) * Compilers (23) * Conferences (28) * Containers (2) * Cryptography (34) * Crytic (2) * Cyber Grand Challenge (7) * DARPA (20) * Dynamic Analysis (12) * Education (14) * Empire Hacking (7) * Engineering Practice (11) * Events (5) * Exploits (27) * Fuzzing (29) * Go (4) * Guides (9) * Internship Projects (27) * iVerify (4) * Kubernetes (2) * Linux (1) * Machine Learning (1) * Malware (7) * Manticore (15) * McSema (11) * Meta (11) * Mitigations (9) * osquery (21) * Paper Review (11) * Podcast (1) * Press Release (24) * Privacy (8) * Products (5) * Program Analysis (15) * Research Practice (16) * Reversing (14) * Rust (4) * SafeDocs (1) * Sinter (1) * Slither (1) * Sponsorships (12) * Static Analysis (24) * Symbolic Execution (17) * Training (1) * Uncategorized (19) * Year in Review (4) * Zero Knowledge (1) My Tweets %d bloggers like this: