FOLLOW THE MECHANISM

  1. 1Private key

    Creates authorization and must remain secret.

  2. 2Public key

    Allows others to verify authorization.

  3. 3Address

    Identifies the relevant destination or spending condition.

A conceptual sequence. Real implementations can add steps, intermediaries, and conditions.

Two different abilities

A private key is secret material used to authorize actions. A public key enables verification without granting the same signing ability. Secure key generation relies on sufficient unpredictable randomness; choosing a memorable number defeats that protection. The relationship is mathematical, not a registration record held by a help desk. For a simple key-controlled account, losing the only usable secret can mean permanently losing the ability to authorize spending.

An address is an identifier

An address is a network-specific encoding used to identify an account or spending condition. It may be derived from a public key, a hash or a contract’s deployment rules. Bitcoin supports several address constructions; Ethereum commonly presents a hexadecimal account address. An address alone does not identify a person or prove that the recipient controls it. Similar-looking formats on different networks do not establish that a transfer is supported.

Authority can be distributed

Not every account depends on one ordinary private key. A multisignature arrangement can require several approvals, while a smart account can define recovery or delegated permissions. These are additional authorization rules implemented by scripts or contracts. The useful question is who can satisfy those rules today, including any administrative or recovery path. A polished wallet interface may conceal a much more complex control structure underneath.

Balances live in the ledger

The key does not contain coins. Nodes maintain ledger state; a key supplies evidence that an allowed state transition was authorized. Copying a key does not copy a balance into a second independent account: both copies can authorize actions against the same state. Likewise, deleting a wallet application does not erase the ledger record. Recoverability depends on the keys and account rules, not the continued existence of one screen.

MAKE IT CONCRETE

One balance, two key copies

In a hypothetical account with 20 units, two devices hold the same signing key. Both display the same 20 units. If one device spends all 20, the second cannot spend another 20: it is referring to the same ledger position. The extra key copy increases access and exposure; it does not create additional assets.

FAILURE PATHS & COMMON MISREADINGS

Where the model can break

  • An address is not a secret key and is not evidence of identity.
  • Backups increase resilience only if unauthorized people cannot also use them.

TRY IT YOURSELF

What did you just sign?

You have 1,000 fictional DEMO tokens. A website asks you to sign something. Inspect the actual request, predict its scope, and decide whether to accept it. Then advance time to test the authority that remains.

Open the scenario 3–5 min · Fictional balances · Replay your decisions

KEEP EXPLORING

Connect this idea

Part of a bigger story

← Back to all topicsBack to top ↑