How Crypto WorksA VISUAL FIELD GUIDESearch
Curious about a word? Tap a dotted term for its meaning.

ROUTE 12 / Go deeper

Find the hidden dependencies

A deeper path through control, ordering, privacy, and governance.

7 ideasAbout 35 minutesRead in order, or choose a step

“Decentralized” does not answer every practical question about a system. Trace where decisions are made, who can alter the code, what data is assumed correct, and what remains visible. The result is a map of dependencies rather than a single trust label.

  1. 01

    Custody and control

    Locate asset control

    Identify who can sign or restrict withdrawals.

  2. 02

    Smart contracts and programmable obligations

    Locate executable rules

    Code can automate rules while retaining upgrade or pause authorities.

  3. 03

    Oracles and outside information

    Locate external data

    Onchain execution still needs a way to learn about outside facts.

  4. 04

    Transaction ordering and MEV

    Locate ordering power

    Transaction ordering can change outcomes and redistribute value.

  5. 05

    Privacy and public ledgers

    Locate exposed information

    Pseudonymous activity can still be linked and analyzed.

  6. 06

    Zero-knowledge proofs

    Locate the statement being proved

    Proof validity and application privacy are different properties.

  7. 07

    How to read a protocol

    Bring the evidence together

    Use contracts, documentation, audits, and control structures to ask precise questions.

CHECK YOUR UNDERSTANDING

Does open source code mean nobody can change a deployed application?

Reveal the explanation

No. Source visibility does not remove proxy upgrades, administrators, governance powers, or dependencies on changeable external components. Examine the actual deployed controls.

Another route through the ecosystemI send a transaction →