
Why Decentralized Currency Must Be Public? Decoding the Overlooked Privacy Choices in Satoshi Nakamoto's Whitepaper
Author: Lithos.eth
Compiled by: TechFlow
TechFlow Summary: While Bitcoin’s public ledger breaks the monopoly of traditional financial intermediaries, it also lays bare all transaction inputs, outputs, and amounts under an unblinking spotlight. As early as Section 10 of the whitepaper, Satoshi Nakamoto clearly identified this architectural flaw and proposed using anonymous public keys as a defense. However, this offers only pseudonymity, not true confidential transactions.
From early blind signatures and zero-knowledge proofs, to on-chain confidential transfers in Monero and Zcash, to programmable privacy for smart contracts in Aztec and Oasis Sapphire, and Ethereum’s Kohaku which addresses wallet query leaks, the crypto space is moving beyond the narrow reliance on single-method mixers. Privacy is never about obscuring everything; it is about granting individuals the power to selectively reveal their data to the world.

Bitcoin allows anyone to independently verify complete transaction histories without seeking bank approval.
Yet, this publicly visible record can easily expose personal privacy far beyond what users initially expect. Satoshi Nakamoto addressed this thorny issue back in Section 10 of the original Bitcoin whitepaper.
Since then, cryptographers and developers have continuously explored technical paths that protect information secrecy while maintaining verifiable transactions. After years of evolution, how far have we truly come?
The moment your Bitcoin payment is confirmed, it becomes an indelible part of the global public ledger.
Anyone in the world can access it at any time.
They can see the source input of every spent coin, the destination output address receiving the funds, the exact amounts allocated to those outputs, and the block height and timestamp when the transaction was packaged and confirmed.
Analysts may not know your real name right away, but once a single address gets linked to an off-chain identity, tracking all your past and future on-chain activities becomes highly straightforward.
Your salary deposits, savings levels, business payments, and daily spending habits could all leave traces on the same public ledger.
For a system originally designed to enable free fund transfers outside the banking sector, this is undoubtedly a thought-provoking compromise and trade-off.
Moreover, Satoshi did not overlook this point. In the original Bitcoin whitepaper, Section 10 is explicitly titled “Privacy.”
To understand the future trajectory of blockchain privacy, we must revisit Satoshi’s original arguments, review the explorations of cryptographic pioneers before Bitcoin’s birth, and objectively assess the advantages and limitations of current privacy solutions.
Before Bitcoin: Pioneers Explored Solutions
Discussions on cryptocurrency privacy did not begin with Bitcoin.
As early as 1982, David Chaum published the seminal paper Blind Signatures for Untraceable Payments.

Figure: 1982 paper by David Chaum on Blind Signatures for Untraceable Payments
In the paper, Chaum explored how users could obtain digitally signed payment certificates without allowing the issuing authority to link the credentials to final transactions.
This concept is crucial because a single payment leaks far more than just fund transfers. It also exposes who transacts with whom, when interactions occur, and transaction frequency.
Chaum’s research established a critical milestone for e-cash, but his model still relied on centralized issuers. Protecting payment information and eliminating trust in central authorities are two distinctly different challenges.
Other researchers and programmers continued exploring in this direction, with the cypherpunk community determined to take bolder steps.
In September 1992, a group of cryptographers, programmers, and privacy advocates organized around a mailing list hosted by John Gilmore, for which Jude Milhon reportedly coined the term “cypherpunk.”
Their interests extended beyond digital currency, passionately debating strong encryption algorithms, anonymous communication protocols, digital identity, freedom of information, and the ability of individuals to protect themselves using open-source software.
Timothy C. May authored The Crypto Anarchist Manifesto in 1988, distributing it online during early movement gatherings in 1992.
Subsequently, on March 9, 1993, Eric Hughes formally published the enduring A Cypherpunk's Manifesto.
One line from the manifesto remains as resonant today, over three decades later: Privacy is necessary for an open society in the electronic age.

Figure: Eric Hughes’ A Cypherpunk's Manifesto, published in 1993
But Hughes raised another, even more profound argument in the manifesto: Privacy is the power to selectively reveal oneself to the world.

Figure: Eric Hughes argued in the manifesto that “privacy is the power to selectively reveal oneself to the world.”
He did not advocate hiding everything, but rather emphasized that individuals must have absolute autonomy over what they present to the outside world.
A merchant selling you a product does not need to audit your entire financial history; a recipient receiving a transfer doesn’t need to peek at every other transaction happening in your wallet.
Hughes stated clearly: both parties in a transaction should only know the information necessary to complete it, leaving extraneous details entirely untouched. This concept remains at the core of privacy discussions today.
Cypherpunks never believed privacy would be granted as a concession; they firmly believed it had to be built through code. Their most famous motto remains: Cypherpunks write code.
The Foundational Ideas Leading to Bitcoin
Bitcoin’s emergence was not sudden. Prior to its release, several pioneers had spent years cultivating different technical components of digital currency.
Hashcash (Adam Back, 1997): A proof-of-work mechanism designed to drastically increase the marginal cost of spamming and specific resource abuse.
b-money (Wei Dai, 1998): A design for an anonymous, distributed electronic cash system.
Bit Gold (Nick Szabo): A proposal for building digital scarcity around computational work, followed by Szabo’s detailed technical exposition in 2005.
Reusable Proof-of-Work (RPOW, Hal Finney, 2004): An attempt to make proof-of-work computation results transferrable as secondary digital tokens.
These explorations varied significantly. Though none directly evolved into Bitcoin and each tackled distinct problems, they collectively charted the rich academic and intellectual ecosystem Satoshi inhabited.
By then, a serious technological movement had already emerged, aiming to construct an independent digital currency completely free from reliance on commercial banks, government agencies, or centralized clearinghouses.
Satoshi’s Bitcoin whitepaper explicitly cited both Hashcash and b-money in its references.

Figure: Citations of Hashcash and b-money in the Bitcoin whitepaper references
Bitcoin synthesized the insights from early research and conquered an incredibly difficult core challenge: How to achieve network-wide consensus on a shared ledger without a centralized arbiter preventing double-spending?
This was a milestone breakthrough in cryptocurrency history, but the trade-off was obvious: all transaction data had to be made publicly accessible across the entire network.
Satoshi’s Genuine Perspective on Privacy
On October 31, 2008, Satoshi released the whitepaper titled “Bitcoin: A Peer-to-Peer Electronic Cash System,” featuring a dedicated Section 10 on privacy.
Opening with this chapter, Satoshi immediately contrasted Bitcoin’s transparent transaction mechanism with the familiar privacy paradigms of traditional banking.
In traditional banking, transactions are completely transparent to the institution, but the general public cannot peek into others’ account balances and statements.
Bitcoin operates on the exact opposite logic: transactions themselves must be broadcast publicly to the entire network, while users’ real identities remain concealed behind anonymous public keys.
Satoshi wrote: “The requirement to publicly publish all transactions eliminates the old methods, but privacy can still be maintained by cutting the information flow elsewhere: keeping public keys anonymous.”
The specific strategy he proposed included generating a new key pair for each transaction, making it harder to trace multiple linked payments back to a single person.
However, Satoshi candidly pointed out a inherent flaw in the model: when a single transaction consumes multiple inputs, those inputs mathematically prove they belong to the same owner.
If just one address becomes linked to a real-world identity, all other on-chain activities associated with it can easily be pieced together.
This marks a crucial conceptual distinction: Bitcoin’s native design provides pseudonymity, not true confidentiality.
Your real name may not be directly recorded on the ledger, but every detail of on-chain transactions is exposed. Auxiliary data from off-chain sources is enough to match on-chain addresses to real individuals.
Satoshi never claimed this was perfect privacy; he simply offered a pragmatic compromise within a distributed system heavily reliant on public verification, aiming to minimize the linkage between transactions and real-world identities as much as possible.

Figure: Comparison of traditional vs. Bitcoin’s new privacy models drawn by Satoshi in Section 10 of the whitepaper
What Can Others See in a Single Bitcoin Transaction?
Let’s examine a concrete everyday payment scenario.
Lithos intends to pay Emma 0.5 BTC. He constructs a payment transaction using existing unspent transaction outputs (UTXOs) from his wallet.
The transaction is broadcast across the network, packaged into a block, and permanently written to the blockchain ledger.
At this point, any external observer can clearly verify the following elements:
· The specific input UTXO consumed in this transaction;
· The target output address receiving the funds;
· The exact Bitcoin amount allocated to each output;
· The transaction fee (precisely calculated from the difference between total inputs and total outputs);
· The exact block height and timestamp when the transaction was confirmed.
An observer might initially not know the real-world identities of Lithos or Emma.
But suppose Lithos’s funds came from a compliant exchange enforcing strict KYC procedures, or Emma previously published her donation address on a personal public website.
Chain analysis investigators could effortlessly tie these addresses to real identities, tracing their entire historical transaction trails.
Real-world scenarios add complexity through change outputs: when a transaction generates change, the leftover funds typically return to the sender rather than going to the recipient.
Blockchain analytics firms often rely on specific algorithmic assumptions to guess which output represents change. While these heuristics aren’t always perfectly accurate, they are sufficient to sketch highly valuable money-flow graphs.
The key takeaway is this: even though Bitcoin never directly records names, its fully transparent transaction history can expose vast amounts of sensitive personal information.
This is precisely why we must never conflate “anonymity” with “privacy” when discussing Bitcoin. Its addresses are pseudonymous, while its base-layer transaction history is completely public.

Satoshi Still Grappled with Privacy Challenges in 2010
There is also a highly instructive episode in Bitcoin’s developmental history.
On August 11, 2010, Satoshi participated in an in-depth technical discussion on the Bitcointalk forum titled “Not a suggestion.”
The core question at the time was: Could Bitcoin avoid storing all historical transaction data completely, as it did in its early days?
The bottleneck in this consideration lies in preventing double-spending: If a network node lacks sufficient information to trace the full transaction history, how can it confirm that a coin hasn’t been spent previously?
Satoshi explained that logically verifying the absence of double-spending requires nodes to possess a global understanding of all relevant transactions across the network.
He then wrote a profoundly significant sentence: “In this situation, it is hard to see how to apply zero knowledge proofs.”

Figure: Satoshi’s 2010 Bitcointalk discussion on zero-knowledge proofs and double-spend verification
The context of this passage is critically important: Satoshi absolutely did not consider zero-knowledge proofs useless. He was tackling a specific technical hurdle: How can a node prove that an asset hasn’t undergone double-spending without holding the complete transaction history?
In other words, how does the network verify a certain type of “absence”? This is a completely different technical dimension from “whether proofs can hide the detailed parameters of a payment.”
Clarifying this historical detail is essential because many contemporary privacy discussions mistakenly assume Satoshi completely overlooked zero-knowledge cryptography back then.
Historical facts are far richer than rumors: Satoshi not only understood the concept of zero-knowledge proofs but also deeply pondered the massive engineering challenges of applying them to Bitcoin’s double-spend verification.
Subsequent cryptographic research took root precisely in this soil: Researchers pioneered a new paradigm using zero-knowledge proofs to conceal transaction details while still allowing network nodes to validate transaction legitimacy.
From Hiding Identities to Concealing Payment Details
The pace of cryptographic research did not slow down as Bitcoin matured.
In 2013, academia published the groundbreaking paper Zerocoin: Anonymous Distributed E-Cash from Bitcoin.

Figure: 2013 publication of the Zerocoin paper Zerocoin: Anonymous Distributed E-Cash from Bitcoin
The paper precisely pinpointed Bitcoin’s critical flaw: a fully transparent ledger architecture means its privacy protection rests entirely on fragile pseudonymity.
Zerocoin explored using cryptography to break the link between transactions and their origins, but it still exposed destination addresses and payment amounts, leaving noticeable limitations in payment flexibility.
By 2014, the research team took another leap forward with Zerocash: Decentralized Anonymous Payments from Bitcoin.
Zerocash introduced non-interactive zero-knowledge proofs (zk-SNARKs), successfully achieving a complete protocol that comprehensively conceals transaction senders, recipients, and transfer amounts while still allowing network nodes to rigorously verify transfer validity.
This represented a profound elevation of Satoshi’s original privacy model.
Bitcoin attempted to decouple public addresses from real-world identities; Zerocash explored how to directly and completely remove transaction data itself from public view.
This marked a milestone shift: decentralized networks do not need to know every plaintext detail of a payment to confirm whether it adheres to monetary rules.
With concise zero-knowledge proofs, the system can mathematically prove to the entire network that a transaction is legitimate and compliant without exposing its construction parameters to anyone.
This is exactly why zero-knowledge cryptography sits at the crown jewel of blockchain privacy research.
What Exactly Do Mainstream Contemporary Privacy Systems Protect?
In everyday discussions about blockchain privacy, people often tend to lump all projects into a single category.
Hiding the recipient does not equal hiding the amount; hiding the amount does not equal hiding the on-chain transaction topology; and hiding on-chain data does not automatically prevent network communication leaks before a transaction is initiated.
We must clearly separate and distinguish these technical schools of thought.
Some systems hide recipients but keep amounts public; others mask transaction amounts but leak query traces at the wallet level or via network RPC nodes; yet other solutions allow users to prove eligibility without exposing their full identity.
These represent security protections across completely different dimensions. Let’s examine a few representative technical implementations.
Bitcoin and Payjoin
Although Bitcoin maintains transparency at the base ledger layer, this does not mean developers have been idle regarding privacy improvements.
Community developers designed mechanisms that drastically reduce the reliability of traditional on-chain graph analysis, among which Payjoin defined in BIP 78 stands out as particularly representative.
Payjoin allows the payer and payee to collaboratively construct a single payment transaction, where the recipient also proactively contributes an input UTXO to the transaction.
Why is this so crucial?
Traditional on-chain tracking usually relies on a core assumption: all input addresses in a single transaction belong to the same person. But if the recipient injects an input in a Payjoin transaction, this universal assumption completely collapses.
Payjoin does not hide transaction amounts nor does it transform Bitcoin into a confidential payment system; it simply greatly increases the difficulty and uncertainty for external entities performing on-chain fund clustering analysis.
This improvement is highly practical, but it must never be confused with end-to-end fully confidential transactions.
Monero
Monero took a different path, natively embedding robust privacy guarantees directly into its underlying transaction mechanism.
It operates through several core cryptographic components working in tandem to comprehensively mask every dimension of a single payment:
· Ring Signatures: Obfuscate the true sender, preventing external observers from identifying which specific output is actually being spent within the decoy ring;
· Stealth Addresses: Generate a unique one-time destination address for every receipt, severing the link between the transfer and the recipient’s public address;
· Ring Confidential Transactions (RingCT): Encrypt and conceal the exact transaction amount while still allowing the network to verify issuance and conservation laws.
However, this system also has boundaries: sender privacy is probabilistic, depending on the configuration of the transaction ring and the auxiliary data available to external observers.
Monero also introduced the Dandelion++ protocol to reduce the physical node traceability of transactions when broadcast on the P2P network, but its official documentation clearly warns: this alone cannot resist all network-level surveillance.
User ISP providers, VPN services, or malicious remote nodes can still potentially capture network-level interaction signals.
Zcash
Zcash transformed Zerocash’s academic research into a mature, deployed cryptocurrency ecosystem.
Its core feature is shielded transactions, leveraging zero-knowledge proofs to conceal core transaction information.
In transfers between shielded addresses, the public ledger completely hides the sender, recipient, transfer amount, and memo contents. Network nodes only need to verify the zero-knowledge proof to ensure asset legitimacy.
This offers a far more robust on-chain confidentiality guarantee than Bitcoin’s native pseudonymous model.
But Zcash simultaneously retains transparent addresses, meaning interactions involving them remain completely visible to the outside world.
The adoption rate of shielded transactions, capital flow paths between transparent and shielded pools, wallet support levels, and overall anonymity set size directly determine the actual privacy protection strength a user receives.
Additionally, Zcash introduced viewing keys, allowing users to disclose transaction details to specific auditors without relinquishing spending authority, demonstrating a design philosophy that “privacy and disclosure are not zero-sum games.”

Figure: On-chain privacy feature comparison between Bitcoin, Payjoin, Monero, and Zcash
It is important to emphasize that the above comparison only describes on-chain information an external observer can extract from the blockchain ledger itself. It does not cover off-chain risks such as IP address leaks, device hacking, or exchange KYC aggregation.
Privacy is never a single static feature; it is a layered defense system where components work in tandem, each playing a distinct role.
New Privacy Challenges for Application-Level Smart Contracts
Since Bitcoin’s inception, the industry’s greatest evolution has extended beyond creating tokens that mask transaction details. It now focuses on embedding privacy principles into the design DNA of smart contracts and decentralized applications.
Today, on-chain behaviors vastly exceed simple transfers: lending staking, decentralized trading, DAO governance voting, portfolio management, and proofs of eligibility.
All these interactions inevitably release sensitive commercial and personal data. Traders don’t want their positions monitored in real-time by the entire network; enterprises refuse to transparently expose treasury flows to competitors; average users need to prove eligibility without exposing their full real-world identities.
Programmable confidential smart contracts were born to resolve this contradiction. Their core goal is enabling decentralized applications to efficiently execute complex operations without publishing every involved data point in plaintext.
Currently, the industry is breaking through from various architectural dimensions:
Aztec: A Layer 2 Balancing Private and Public Functions
Aztec is committed to building a privacy-focused Layer 2 on Ethereum. At the code level, its smart contracts allow developers to flexibly mix declarations of private and public functions.
The core dividing line lies in where the code executes:
Private functions deploy and execute within the Private Execution Environment (PXE) on the user’s local device, completing confidential computations locally and generating corresponding zero-knowledge proofs before only submitting the proof to the network;
Public functions execute instead within network-wide sorters and nodes, utilizing globally readable public state. A single on-chain interaction can seamlessly bridge both.
Taking decentralized anonymous voting as an example: voters cast and sign their ballots securely within the local private environment without disclosing their specific choices externally. Public functions then aggregate vote totals uniformly on-chain. The entire network can verify the final tally accuracy but cannot reverse-engineer individual ballots.
Yet this approach is not without limitations: when a local client queries network state from remote nodes, those remote nodes can still learn which specific data the user is monitoring. Running a full node further mitigates this kind of information leakage.
Oasis Sapphire: Confidential Contracts Based on Hardware Trusted Execution Environments (TEE)
Differing from Aztec’s focus on client-side proofs, Oasis Sapphire employs an entirely different technical paradigm: running confidential smart contracts within hardware-isolated trusted execution environments.
Trusted execution environments rely on physical hardware isolation to protect executing code and confidential data. Sapphire supports fully encrypted transaction inputs and confidential smart contract internal states, enabling contracts to safely process sensitive parameters.
Client-side zero-knowledge proofs and hardware TEEs each carry distinct trade-offs: TEE introduces a trust prerequisite in hardware manufacturer security and microcode implementation, whereas zero-knowledge systems rely on flawless arithmetic circuit design and mathematical proof frameworks.
Umbra: Focused on Internal Transfers Within Shielded Pools
Within the Solana ecosystem, Umbra demonstrated an architectural leap from V1 to V2.
V1 utilized encrypted token accounts as intermediaries for entering shielded pools, while V2 was comprehensively rebuilt into a fund-flow system centered around the shielded pool, allowing users to conduct direct confidential transfers entirely within the pool.
However, it must be recognized: depositing and withdrawing from the shielded pool still leaves on-chain clues. Specific amounts and time windows for inflows and outflows could still provide breadcrumbs for chain analysis, meaning its core privacy protection centers on the internal pool transfer phase.
Privacy Pools: Enabling Selective Compliance Disclosure
Built by the 0xbow team, Privacy Pools is a compliance-focused privacy protocol deployed across multiple chains in the Ethereum ecosystem, inspired by an academic paper co-authored by Vitalik Buterin and others in 2023.
Users deposit assets from standard wallets into the shielded pool. Association Set Providers (ASPs) screen incoming funds to filter illicit capital, while the entire system avoids centralized KYC processes and global backdoor viewing keys.
During withdrawals, users leverage zero-knowledge proofs to demonstrate their funds belong to a screened, compliant set without disclosing exactly which deposit they are spending. This protects lawful personal financial privacy while cutting off the possibility of illicit funds contaminating the compliant pool.
This is a perfect manifestation of Eric Hughes’ selective disclosure concept in modern DeFi: compliance and privacy are no longer mutually exclusive.
Kohaku Confronts a Core Pain Point: What Does Your Wallet Expose Before a Transaction?
In blockchain privacy, there exists another critical yet long-overlooked vulnerability.
Even if a user employs top-tier confidential transaction protocols, they might accidentally leak everything beforehand through routine network requests originating from the wallet itself.
When a wallet opens to refresh its account balance, it typically initiates a data query toward remote RPC nodes. This request directly informs the service provider exactly which address the user is closely monitoring.
Similar leaks frequently occur during routine operations like querying historical transaction logs, pre-executing contract simulations, or fetching token metadata. While the transaction itself might be confidential, the network requests sent prior to it are riddled with vulnerabilities.
This is exactly the frontier arena where Ethereum ecosystem privacy project Kohaku is focusing its efforts. As an open-source privacy-preserving wallet and SDK specification, Kohaku aims to rebuild defensive lines from the foundational level of wallet infrastructure.
Kohaku incorporates Private Information Retrieval (PIR) technology: In traditional balance queries, the server receives a plaintext address and returns data. Under the PIR framework, the wallet constructs special encrypted queries that allow the server to return the targeted result while remaining completely unable to determine exactly which account the user queried.
Wallets serve as the primary gateway for users managing private keys, accounts, signing permissions, and application interactions. If this entry point continuously leaks metadata, relying solely on underlying confidential transactions can never form a secure closed loop.
Have We Surpassed Satoshi’s Privacy Model?
Viewed through specific technical metrics, the answer is undeniably yes.
Satoshi’s initial design was built on pseudonymous public keys and fully transparent transaction history. Yet in today’s crypto landscape:
Regarding transaction confidentiality, Monero and Zcash’s shielded transactions have achieved comprehensive on-chain concealment of inputs, outputs, and amounts—a feat Satoshi himself could not realize at the time;
Regarding verifiable computation, modern zero-knowledge proof systems can mathematically prove to the entire network that complex logic has been executed compliantly without exposing plaintext inputs;
Regarding application expansion, Aztec brings programmable privacy contracts, Oasis Sapphire enables hardware-based confidential computing, Privacy Pools pioneers selective compliance disclosure, and Kohaku tackles wallet client query leaks.
However, if asked whether the privacy problem has been completely solved, the answer remains no.
A confidential transaction cannot hide physical IP exposure during broadcasting; a privacy contract cannot erase temporal patterns in public function interactions; a shielded pool cannot negate capital correlation when funding or withdrawing; TEE hardware cannot escape security assumptions tied to chip manufacturers; and elegant mathematical proofs cannot protect a local device already compromised by malware.
Genuine privacy security must encompass the entire value chain: from terminal wallets and physical hardware to application interfaces, network transmission, smart contracts, and finally, settled on-chain data.
What Should Be Public, and What Must Remain Private?
For years, the blockchain industry has rested firmly on the cornerstone of global public state.
Total transparency grants permissionless independent verification capabilities, but it also lays bare the lives and financial veins of ordinary individuals and commercial entities.
We do not advocate locking all blockchain information into a black box. This is precisely the core logic behind “selective disclosure”:
Public governance bodies and public fiscal expenditures must remain transparent and sunlit, accepting strict oversight from society, while network rule compliance must allow for universal verifiability;
but ordinary citizens’ private savings, salary income, daily micropayments, investment positions, and commercial contracts should absolutely never be forced to lay themselves completely bare to the world simply because blockchain technology was used.
These two ideals can perfectly coexist: Individuals can prove eligibility to service providers without surrendering their entire life records; businesses can settle accounts smoothly without exposing their financial strategies to competitors; voters can cast a sacred ballot while election outcomes remain publicly auditable; and wallets can query assets without exposing any specific accounts to service providers.
This is not about pursuing absolute invisibility; it is about defending control over one’s own data.
As Eric Hughes famously wrote decades ago: Privacy is the power to selectively reveal oneself to the world.
Bitcoin Opened the Curtain, But the Journey is Far from Over
Every time we revisit Satoshi’s words penned in Section 10 of the whitepaper, what inspires the deepest respect is not that Bitcoin definitively solved every privacy proposition forever, but that from day one, Satoshi clearly perceived the profound tension between public ledgers and personal privacy, offering a pragmatic engineering balance tailored to the technological constraints of that era.
The relentless inquiry pursued by cypherpunks over decades remains unchanged: How can people enjoy digital convenience without being forced to surrender personal data that ought never to be peered into?
Bitcoin took the most crucial first step for this era, and subsequent researchers and engineers continue forging ahead along this path.
When evaluating contemporary privacy projects, we cannot merely rest on project marketing slogans, trendy cryptographic jargon, or simplistic “supports confidentiality” badges.
We must coldly scrutinize: What exactly does this system conceal? What information remains glaringly exposed? Upon whose credibility does its security premise rest? And what truly happens when it operates in the real commercial world?
The original question posed by cypherpunks still warrants deep reflection for every practitioner today: By what right does a technical system demand to know extraneous information beyond what is strictly necessary to perform its core duties?
Bitcoin enabled us to achieve monetary verifiability without banks. The puzzle piece that contemporary privacy systems strive to complete is ensuring that, while safeguarding this verifiability, the dignity and power to choose how we present ourselves are returned intact to every independent individual.
References & Further Reading
Early Digital Cash and Cypherpunks
· David Chaum, Blind Signatures for Untraceable Payments (1982)
· Timothy C. May, The Crypto Anarchist Manifesto (1988)
· Eric Hughes, A Cypherpunk's Manifesto (1993)
· Wei Dai, b-money (1998)
· Adam Back, Hashcash (1997)
Bitcoin and Its Privacy Model
· Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System (2008), Section 10
· Satoshi Nakamoto, Bitcointalk discussion: Not a suggestion (2010)
· BIP 78: A Simple Payjoin Proposal
Privacy Academic Research and Frontier Protocols
· Miers et al., Zerocoin (IEEE S&P, 2013)
· Ben-Sasson et al., Zerocash (IEEE S&P, 2014)
· Monero Technical Specifications & Dandelion++
· Zcash Documentation: Addresses and Value Pools
· Aztec Network: Private Execution Environment (PXE)
· Oasis Sapphire Confidential EVM Documentation
· Umbra V2 Shielded Pool Documentation
· Privacy Pools (0xbow) Research Paper & Documentation
· Kohaku: Ethereum Privacy Preserving Wallet & SDK
· Ethereum Foundation Reads: PIR for Wallets
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News















