What is a Wallet Address?

An address is the string you hand to someone so they can pay you. It’s derived from cryptography tied to your keys, but it isn’t your key — publishing it is normal; publishing your seed or private key is not.

Chains disagree on formatting: Bitcoin uses base58check / bech32 styles, Ethereum uses 0x-prefixed hex, Solana uses base58 blobs. The mental model is the same: “where should this ledger entry land?”

Wallets generate a large random secret, derive a public key with elliptic-curve math, then hash and encode until the chain’s spec is satisfied. You cannot “look up” the private key from an address without breaking modern crypto — that’s the point.

HD wallets (BIP-32/39/44) stretch one seed into a tree of keys so one backup can restore many accounts. MPC setups skip the “one seed in a drawer” story and split the secret — different UX, same on-chain address shape once derived.

Bitcoin: Legacy 1…, wrapped SegWit 3…, native SegWit bc1…. Fees and error detection differ; most new wallets default to bc1.

EVM: Checksummed 0x addresses; same bytes on Polygon, Arbitrum, Base — wrong network still loses you time and gas, not necessarily coins, if you can bridge back.

Solana: Short base58 strings; easy to fat-finger — use QR or your address book.

Receiving: open Receive, pick the asset, copy or show QR. Sending: paste the recipient, triple-check prefix and network, leave room for gas. Everything on-chain is final — no chargeback department.

Clipboard malware is real: glance at more than four characters at each end. For chunky transfers, a tiny test payment still saves grief.

Use labeled address book entries, rotate receive addresses where it matters for privacy, and ignore “dust” payments from look-alike senders (address poisoning). When in doubt, ask the counterparty to confirm the string out-of-band.

GaiaEx stays non-custodial: you sign, assets settle on-chain. MPC backing means the familiar “one seed on paper” story may be abstracted, but the address you share is still yours — the interface should surface network and asset clearly so you don’t learn about mismatches from a failed explorer lookup.