21wiki

Third Parties (and Why Bitcoin Removes Them)

3 min read

What the Sources Mean by “Third Parties”

In the “trusted third parties are security holes” framing (Nick Szabo), a trusted third party (TTP) is not “a helpful service” — it is a security vulnerability: a place where a protocol quietly assumes a third party will behave correctly, stay available, resist coercion, and not abuse power.

Szabo’s suggested language swap is blunt and useful: “trusted” often really means “vulnerable to.”

Source: Trusted Third Parties Are Security Holes

Why Intermediaries Exist in Legacy Money

Inventing Bitcoin models banks and payment processors as centralized ledgers (databases) that:

  • Authenticate users (accounts, passwords, KYC)
  • Enforce ordering (preventing double spending)
  • Reverse or refuse transactions

This works — but it concentrates control and creates a single point that can be coerced, hacked, censored, or used for rent extraction.

Source: Inventing Bitcoin — Ch. 2

How Bitcoin Removes the Need to Trust Them

Bitcoin replaces “a ledger you can access only through the bank” with:

The point is not “no one provides services.” It is that the base layer does not require trusting a specific institution to define balances, settle finality, or allow participation.

See also the network-wide coordination and incentive framing in “Bitcoin is an idea”: Bitcoin as an unstoppable protocol-level idea that persists beyond any single organization.

Source: 21 Ways — Ch. 1: Bitcoin is an idea

What Bitcoin Does Not Eliminate

The sources imply a crucial distinction:

  • Protocol-level trust minimization: anyone can validate; no privileged ledger operator is required.
  • Service-level convenience: exchanges, hosted wallets, explorers, and custodians can exist — but they reintroduce third-party risk.

This is why self-custody and running your own node are framed as sovereignty tools: they reduce reliance on external TTPs.

Sources

Graph View

Backlinks