Wallets, keys and addresses: the only mental model you need
Private keys sign, public addresses receive, wallets manage the difference. The three ideas that make everything else click.
暂无该语言版本——显示英文。
The three objects
A private key is a large secret number. A public address is derived from it by one-way math: easy to compute forward, infeasible to reverse. A wallet is software (or hardware) that stores your private keys and builds transactions for you to sign.
That is the whole model. Everything in Web3 — exchanges, bridges, agents, vaults — is machinery around these three objects.
What signing actually proves
When you "connect a wallet" and approve an action, your wallet signs a message with the private key. The chain verifies the signature against your address. At no point does the private key travel anywhere: the signature proves control without revealing the secret.
This is why JW3's terminal can route your trades without custody — the browser signs locally, and only signed instructions ever leave your device.
Addresses are safe to share, keys are not
Give your address to anyone who pays you. Never type your private key or seed phrase into any website, form, or chat — no legitimate product ever asks for it. Support agents, airdrops, and "validators" that request keys are always theft.
Seed phrases are keys in readable form
Most wallets derive all your keys from one 12- or 24-word seed phrase. Whoever holds the words controls every address the wallet will ever generate. Back it up on paper or metal, stored offline, in a place that survives fire and forgetfulness.
Risk note: cryptocurrency trading, leveraged perpetual futures, and automated algorithmic strategies carry significant risk of rapid and total financial loss. Never risk funds you cannot afford to lose completely. Nothing in this lesson is investment advice, a recommendation, or an offer to sell any product.
清单
- I can explain why an address is safe to share and a private key is not
- I know where my wallet stores its keys