PrevNext

Academy Node

Address vs Public Key

🧱 Primitive

Type: PrimitiveDifficulty: 2/4address-vs-public-keyVerified: 2026-02-12

Summary

Addresses are encoded script destinations, while public keys are cryptographic primitives used for signature verification.

Story

A beginner copies an address and assumes it is the same thing as a public key. In legacy and modern script types, that shortcut fails. Addresses are human-friendly encodings of script templates or key hashes. Public keys are cryptographic points used in signature checks. With SegWit2017 Bitcoin upgrade separating witness data, fixing transaction malleability vectors, and improving capacity efficiency. and Taproot2021 Bitcoin soft fork adding Schnorr signatures and improved script-path privacy/efficiency., this distinction became even more important because address formats signal spending semantics and checksum protections. Getting this right helps users avoid compatibility mistakes, understand why some outputs reveal keys only at spend time, and appreciate why address parsing is not just cosmetic formatting.

Deep Dive

Encoding layers

  • Base58 and Bech32/Bech32m encode destination data with checksums.
  • Addresses often represent hashes or scripts, not raw public keys.
  • Output type determines witness structure and spending path behavior.

Security implications

  • Address checksum failures catch many copy/paste errors.
  • Misinterpreting address type can cause wallet interoperability issues.
  • Taproot2021 Bitcoin soft fork adding Schnorr signatures and improved script-path privacy/efficiency. key-path and script-path semantics require correct bech32m handling.

Real Data

Current Format Epoch

Loading...

Height context for modern address adoption patterns.

Address Parsing Snapshot

Loading...

Timestamp for latest protocol-state context shown in Raw Block.

Key Takeaways

  • Address != public key in modern Bitcoin usage.
  • Address format conveys script semantics and checksum model.
  • SegWit2017 Bitcoin upgrade separating witness data, fixing transaction malleability vectors, and improving capacity efficiency./Taproot2021 Bitcoin soft fork adding Schnorr signatures and improved script-path privacy/efficiency. upgrades changed destination encoding expectations.

Security Notes

  • Checksum validation reduces accidental address corruption.
  • Type confusion can lead to failed sends or incompatible spend scripts.

Node Security Panel

Vulnerabilities (0)

    Attacks (0)

      Assumptions (0)

        Policy vs Consensus (0)

          Policy vs Consensus

          Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. validates scripts and signatures; policy/UI layers map user-readable addresses to those Consensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. objects.

          Consensus Rules

          • ConsensusConsensus RulesNetwork-wide validation rules every full node enforces to determine valid blocks and transactions. validates script execution regardless of user-facing address label.
          • ConsensusWitness and script rules enforce spend-path correctness per output type.

          Policy Rules

          • PolicyWallet policy may restrict unsupported address/script templates.
          • PolicyExchange policy can limit withdrawals to selected destination types.

          Security Research Panel

          Bech32m Deployment for Taproot

          2021

          Address parsing updates were required to safely support Taproot2021 Bitcoin soft fork adding Schnorr signatures and improved script-path privacy/efficiency. outputs and avoid accidental send failures.

          Explorer Deep Links

          Some sources are external. When an internal Raw Block view is available, we'll surface it here.

          Claim Sources

          Bech32 and bech32m define modern address encodings for SegWit and Taproot.

          Addresses encode script destinations and are not always raw public keys.

          Claim Registry Links

          • Bitcoin addresses are encoded destinations derived from scripts/keys and are not identical to raw public keys.

            Verified: 2026-02-12

            Source

          Further Reading

          Graph Neighbors

          DirectionRelationNode
          OutgoingDEPENDS_ONPseudonymity, Not Anonymity
          IncomingDEPENDS_ONWallets Hold Keys, Not Coins

          Related Nodes