pith. sign in

arxiv: 1906.11078 · v1 · pith:KWOXNBIMnew · submitted 2019-06-26 · 💻 cs.CR · cs.DB

Blockchain Technology Overview

Dylan Yaga , Peter Mell , Nik Roby , Karen Scarfone This is my paper

Pith reviewed 2026-05-25 15:36 UTC · model grok-4.3

classification 💻 cs.CR cs.DB
keywords blockchaindistributed ledgertamper evidenttamper resistantdigital ledgerdecentralized authoritytransaction recording
0
0 comments X

The pith

Blockchains are tamper evident and tamper resistant digital ledgers implemented in a distributed fashion without a central authority.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

This paper supplies a high-level technical overview of blockchain technology to explain its basic operation. It defines blockchains as distributed digital ledgers that allow communities to record transactions such that no transaction can be changed once published under normal network conditions. The overview emphasizes the absence of a central repository or authority while highlighting the tamper-evident and tamper-resistant properties that result from the distributed structure. A sympathetic reader would care because the description isolates the core features that enable shared record-keeping without traditional intermediaries.

Core claim

Blockchains are tamper evident and tamper resistant digital ledgers implemented in a distributed fashion (i.e., without a central repository) and usually without a central authority (i.e., a bank, company, or government). At their basic level, they enable a community of users to record transactions in a shared ledger within that community, such that under normal operation of the blockchain network no transaction can be changed once published.

What carries the argument

The distributed ledger mechanism that records transactions across a network of users so that published entries become tamper evident and tamper resistant without requiring a central authority.

If this is right

  • Communities can maintain a shared transaction record whose entries remain unchanged once published.
  • The ledger operates without a central repository or authority for validation and maintenance.
  • Transactions gain tamper evidence and resistance directly from the distributed network structure.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The properties described could provide a baseline for assessing data integrity in other decentralized record systems.
  • Readers might connect these ledger features to questions of scalability when networks grow in size.
  • The overview leaves room for testing whether specific implementations preserve the stated tamper resistance under real-world network partitions.

Load-bearing premise

The high-level description in the document accurately captures the essential properties of blockchain technology as it existed at the time of writing.

What would settle it

A concrete demonstration that a published transaction on an operating blockchain network can be altered without detection or violation of normal conditions would falsify the central claim.

Figures

Figures reproduced from arXiv: 1906.11078 by Dylan Yaga, Karen Scarfone, Nik Roby, Peter Mell.

Figure 3
Figure 3. Figure 3: Generic Chain of Blocks................................................................................. 17 [PITH_FULL_IMAGE:figures/full_fig_p011_3.png] view at source ↗
read the original abstract

Blockchains are tamper evident and tamper resistant digital ledgers implemented in a distributed fashion (i.e., without a central repository) and usually without a central authority (i.e., a bank, company, or government). At their basic level, they enable a community of users to record transactions in a shared ledger within that community, such that under normal operation of the blockchain network no transaction can be changed once published. This document provides a high-level technical overview of blockchain technology. The purpose is to help readers understand how blockchain technology works.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

0 major / 1 minor

Summary. The manuscript provides a high-level technical overview of blockchain technology. It defines blockchains as tamper-evident and tamper-resistant digital ledgers implemented in a distributed fashion (without a central repository) and usually without a central authority, enabling a community of users to record transactions in a shared ledger such that no transaction can be changed once published under normal network operation. The stated purpose is to help readers understand how the technology works.

Significance. If the descriptions hold, the document offers a concise, accessible reference for the core properties of blockchain systems as understood in 2019. Its value lies in standardizing basic terminology and concepts for a technical audience rather than advancing novel results or proofs.

minor comments (1)
  1. [Abstract] The abstract states the central definition clearly but does not preview the document's organization or the specific technical topics (e.g., consensus mechanisms, data structures) that will be covered in subsequent sections.

Simulated Author's Rebuttal

0 responses · 0 unresolved

We thank the referee for the positive review and recommendation to accept. There are no major comments to address.

Circularity Check

0 steps flagged

No significant circularity

full rationale

The paper is a high-level NIST technical overview document whose content consists entirely of descriptive explanations of blockchain concepts, properties, and implementations. It contains no equations, derivations, fitted parameters, predictions, or novel technical results. The central claim is a standard definitional statement of blockchain properties (tamper-evidence/resistance, distributed ledger without central repository/authority). No load-bearing steps reduce to self-definition, fitted inputs, or self-citation chains. The document is self-contained as a descriptive summary against external benchmarks and requires no circularity analysis.

Axiom & Free-Parameter Ledger

0 free parameters · 0 axioms · 0 invented entities

This is a review paper summarizing existing technology and introduces no free parameters, axioms, or invented entities.

pith-pipeline@v0.9.0 · 5602 in / 881 out tokens · 27020 ms · 2026-05-25T15:36:19.787272+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

39 extracted references · 39 canonical work pages

  1. [2]

    (Preimage resistant) It is computationally infeasible to compute the correct input value given some output value (the hash function is ‘one way’)

    work page

  2. [3]

    (Second preimage resistant) One cannot find an input that hashes to a specific output

    work page

  3. [4]

    See the NIST SP 800-175B Guideline for Using Cryptographic Standards in the Federal Government: Cryptographic Mechanisms, http://dx.doi.org/10.6028/NIST.SP.800-175B

    (Collision resistant) It is computationally infeasible to find any two distinct inputs that map to the same output. See the NIST SP 800-175B Guideline for Using Cryptographic Standards in the Federal Government: Cryptographic Mechanisms, http://dx.doi.org/10.6028/NIST.SP.800-175B. Cryptographic nonce An arbitrary number that is used once. Decentralized ne...

    work page doi:10.6028/nist.sp.800-175b

  4. [5]

    Hazards of Prophecy: The Failure of Imagination,

    Clarke, A.C., “Hazards of Prophecy: The Failure of Imagination,” from Profiles of the Future: An Inquiry into the Limits of the Possible, 1962

    work page 1962

  5. [6]

    The Part-Time Parliament

    Lamport, Leslie. “The Part-Time Parliament.” ACM Transactions on Computer Systems, vol. 16, no. 2, Jan. 1998, pp. 133–169., https://dl.acm.org/citation.cfm?doid=279227.279229

    work page arXiv 1998

  6. [7]

    Narayanan, A., Bonneau, J., Felten, E., Miller, A., and Goldfede, S., Bitcoin and Cryptocurrency Technologies: A Comprehensive Introduction, Princeton University Press, 2016

    work page 2016

  7. [8]

    Bitcoin: A Peer-to-Peer Electronic Cash System,

    Nakamoto, S., “Bitcoin: A Peer-to-Peer Electronic Cash System,” 2008. https://bitcoin.org/bitcoin.pdf

    work page 2008

  8. [9]

    https://doi.org/10.6028/NIST.FIPS.180-4

    National Institute of Standards and Technology, Secure Hash Standard (SHS), Federal Information Processing Standards (FIPS) Publication 180-4, August 2015. https://doi.org/10.6028/NIST.FIPS.180-4

    work page doi:10.6028/nist.fips.180-4 2015

  9. [10]

    National Institute of Standards and Technology (NIST), Secure Hashing website, https://csrc.nist.gov/projects/hash-functions

    work page

  10. [11]

    Hash per Second

    “Hash per Second.” Bitcoin Wiki, http://en.bitcoin.it/wiki/Hash_per_second

    work page

  11. [12]

    https://doi.org/10.6028/NIST.FIPS.202

    National Institute of Standards and Technology, SHA-3 Standard: Permutation- Based Hash and Extendable-Output Functions, Federal Information Processing Standards (FIPS) Publication 202, August 2015. https://doi.org/10.6028/NIST.FIPS.202

    work page doi:10.6028/nist.fips.202 2015

  12. [13]

    https://doi.org/10.6028/NIST.FIPS.186-4

    National Institute of Standards and Technology (NIST), Digital Signature Standard, Federal Information Processing Standards (FIPS) Publication 186-4, July 2013. https://doi.org/10.6028/NIST.FIPS.186-4

    work page doi:10.6028/nist.fips.186-4 2013

  13. [14]

    LDAP.com

    “LDAP.com.” LDAP.com, https://www.ldap.com

    work page

  14. [15]

    How Is the Address of an Ethereum Contract Computed?

    “How Is the Address of an Ethereum Contract Computed?” Ethereum Stack Exchange, 29 Jan. 2016, 22:14, https://ethereum.stackexchange.com/questions/760/how-is-the-address-of-an- ethereum-contract-computed

    work page 2016

  15. [16]

    Making BFT Protocols Really Adaptive,

    Bahsoun, J.P., Guerraoui, R., and Shoker, A., “Making BFT Protocols Really Adaptive,” 2015 IEEE International Parallel and Distributed Processing Symposium, Hyderabad, India, pp. 904-913, 2015. https://doi.org/10.1109/IPDPS.2015.21

    work page doi:10.1109/ipdps.2015.21 2015

  16. [17]

    Time, Clocks, and the Ordering of Events in a Distributed System

    Lamport, L. “Time, Clocks, and the Ordering of Events in a Distributed System.” Communications of the ACM, vol. 21, no. 7, January 1978, pp. 558–565., doi:10.1145/359545.359563. https://amturing.acm.org/p558-lamport.pdf

    work page doi:10.1145/359545.359563 1978

  17. [19]

    Everything you need to know about the Ethereum ‘hard fork,’

    Wong, J. and Kar, I., “Everything you need to know about the Ethereum ‘hard fork,’” Quartz Media, July 18, 2016. https://qz.com/730004/everything-you-need- to-know-about-the-ethereum-hard-fork/

    work page 2016

  18. [20]

    https://doi.org/10.6028/NIST.IR.8105

    Chen, L., Jordan, S., Liu, Y.-K., Moody, D., Peralta, R., Perlner, R., and Smith- Tone, D., Report on Post-Quantum Cryptography, National Institute of Standards and Technology Internal Report (NISTIR) 8105, April 2016. https://doi.org/10.6028/NIST.IR.8105

    work page doi:10.6028/nist.ir.8105 2016

  19. [21]

    Smart Contracts,

    Szabo, N. “Smart Contracts,” 1994. http://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/ LOTwinterschool2006/szabo.best.vwh.net/smart.contracts.html

    work page 1994

  20. [22]

    Cryptocurrency Smart Contracts for Distributed Consensus of Public Randomness

    Mell, P., Kelsey, J., and Shook, J., “Cryptocurrency Smart Contracts for Distributed Consensus of Public Randomness.” October 7, 2017. https://doi.org/10.1007/978-3-319-69084-1_31

    work page doi:10.1007/978-3-319-69084-1_31 2017

  21. [23]

    Majority Attack

    “Majority Attack.” Bitcoin Wiki, https://en.bitcoin.it/wiki/Majority_attack

    work page

  22. [24]

    The Blockchain Immutability Myth

    Greenspan, G. “The Blockchain Immutability Myth.” CoinDesk, May 9, 2017, https://www.coindesk.com/blockchain-immutability-myth/

    work page 2017

  23. [25]

    Analyzing the 2013 Bitcoin fork: centralized decision-making saved the day,

    Narayanan, A., “Analyzing the 2013 Bitcoin fork: centralized decision-making saved the day,” MultiChain, July 28, 2015. https://freedom-to- tinker.com/2015/07/28/analyzing-the-2013-bitcoin-fork-centralized-decision- making-saved-the-day

    work page 2013

  24. [26]

    Blockchain Oracles, Explained

    Buck, J. “Blockchain Oracles, Explained.” Cointelegraph, October 18, 2017, https://cointelegraph.com/explained/blockchain-oracles-explained

    work page 2017

  25. [27]

    https://medium.com/@kleffew/truthpoint-angelhacks-dc-submission- 5569252d795a

    work page

  26. [28]

    The Blockchain Immutability Myth,

    Greenspan, G., “The Blockchain Immutability Myth,” MultiChain, May 4, 2017. https://www.multichain.com/blog/2017/05/blockchain-immutability-myth/

    work page 2017

  27. [29]

    Bitcoin's Growing Energy Problem

    de Vries, A. “Bitcoin's Growing Energy Problem.” Joule, vol. 2, no. 5, 16 May 2018, pp. 801–805., https://doi.org/10.1016/j.joule.2018.04.016

    work page doi:10.1016/j.joule.2018.04.016 2018

  28. [30]

    Bitcoin Could Consume as Much Electricity as Denmark by 2020,

    Deetman, S., “Bitcoin Could Consume as Much Electricity as Denmark by 2020,” Motherboard, March 29, 2016. https://motherboard.vice.com/en_us/article/bitcoin-could-consume-as-much- electricity-as-denmark-by-2020

    work page 2020

  29. [31]

    Bitcoin mining consumes more electricity a year than Ireland,

    Hern, A., “Bitcoin mining consumes more electricity a year than Ireland,” The Guardian, November 27, 2017. https://www.theguardian.com/technology/2017/nov/27/bitcoin-mining-consumes- electricity-ireland

    work page 2017

  30. [32]

    Power Compare, https://powercompare.co.uk/bitcoin/

    work page

  31. [33]

    Bitcoin's Power Needs May Be Overblown

    Loh, T. “Bitcoin's Power Needs May Be Overblown.” Bloomberg.com, Bloomberg, January 16, 2018, https://www.bloomberg.com/news/articles/2018- 01-16/bitcoin-s-power-needs-may-be-overblown-recalling-pot-growing. NISTIR 8202 BLOCKCHAIN TECHNOLOGY OVERVIEW 57 This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8202

    work page doi:10.6028/nist.ir.8202 2018

  32. [34]

    Blockchain Size

    “Blockchain Size.” Blockchain.com, www.blockchain.com/charts/blocks-size. Accessed July 19, 2018

    work page 2018

  33. [35]

    ACT-IAC White Paper: Enabling Blockchain Innovation in the U.S. Federal Government

    “ACT-IAC White Paper: Enabling Blockchain Innovation in the U.S. Federal Government.” ACT-IAC, February 27, 2018, https://www.actiac.org/act-iac- white-paper-enabling-blockchain-innovation-us-federal-government

    work page 2018

  34. [36]

    ACT-IAC White Paper: Blockchain Playbook for the U.S. Federal Government

    “ACT-IAC White Paper: Blockchain Playbook for the U.S. Federal Government.” ACT-IAC, April 23, 2018, https://www.actiac.org/act-iac-white-paper-blockchain- playbook-us-federal-government

    work page 2018

  35. [37]

    Do You Need a Blockchain?

    Wüst, K., Gervais, A. “Do You Need a Blockchain?” IACR ePrint Archive, 2017, p. 375., https://eprint.iacr.org/2017/375.pdf

    work page 2017

  36. [38]

    Do You Need a Blockchain?

    “Do You Need a Blockchain?” Do You Need a Blockchain?, http://doyouneedablockchain.com/

    work page

  37. [39]

    Do You Need a Blockchain?

    Peck, Morgen E. “Do You Need a Blockchain?” IEEE Spectrum: Technology, Engineering, and Science News, IEEE Spectrum, September 29, 2017, https://spectrum.ieee.org/computing/networks/do-you-need-a-blockchain

    work page 2017

  38. [40]

    Don't Use a Blockchain Unless You Really Need One

    Hochstein, M. “Don't Use a Blockchain Unless You Really Need One.” CoinDesk, CoinDesk, 16 Jan. 2018, https://www.coindesk.com/dont-use-blockchain-unless- really-need-one/

    work page 2018

  39. [41]

    Do You Need A Blockchain

    Chand, M. “Do You Need A Blockchain.” C# Corner, January 4, 2018, https://www.c-sharpcorner.com/article/do-you-need-a-blockchain2/

    work page 2018