Understanding keys & seeds

Short version: a public key is your account number — safe to share. A private key is the password that spends from it — never share it. A seed phrase is a master key that can generate private keys for many chains and many addresses, which is powerful and a little unnerving. Wallets handle the math; you handle the backup.

1. Every chain speaks its own key language

A "key" on a blockchain is really just a big number — but every chain dresses that number up in its own costume. The number does the same job (prove ownership, authorize a spend), yet the way it's written down looks completely different from chain to chain. That's why a TEXITcoin address, a Bitcoin address, an Ethereum address and a ZCU address don't look anything alike, even though the math underneath is cousins.

Public key = your account number This is what you give people so they can pay you. It's safe to share — knowing it doesn't let anyone spend your coins. On TEXITcoin it usually starts with a capital T; on Ethereum it starts with 0x.

Private key = the password This is the secret half. Whoever holds it can spend the coins. That's the whole game. Some chains write it as a long string of letters and numbers; some let you express it as a seed phrase instead. Never share either one.

The formats you'll bump into around here:

• TEXITcoin (TXC) — legacy addresses start with T (base58, 26–35 characters). There's also a newer txc1… bech32 format. The Omni Layer 2 — where TSD lives — only recognises the legacy T format. See the wallets guide.
• IskanderCoin (ISK) — same family as TXC but a different address version byte, so valid addresses start with K, I, or L.

Why the prefixes differ: version bytes. The first byte of a base58 address is the version byte — it tells the chain which address format to expect, and it's what makes the first character change. Bitcoin's is 0, Litecoin's is 2, TEXITcoin's is 696969 (Bobby's idea — big enough to never collide with any real coin), and IskanderCoin's is 969696. That's why a TXC address starts with T and an ISK address starts with K, I, or L even though both descend from the same codebase. The point worth remembering: TXC is not 2. It may share a family tree with Litecoin, but its version byte — and its BIP44 coin type — is 696969, its own thing.

• Zero Chill (ZCU) — its own chain with its own address prefix. Same idea, different costume.
• Ethereum / EVM — addresses start with 0x followed by 40 hex characters. This is where USDC commissions land.

The point: the format is the chain's business. You don't convert a TXC address into an Ethereum address any more than you convert a US phone number into a UK one by retyping it. You just get the right address for the right chain and paste it in the right field. Mix them up and the money is gone — not because someone stole it, but because nobody on the receiving chain can read it.

2. The magic seed phrase unlocks many of them

Here's where it gets interesting. Instead of writing down one giant private key per address, most modern wallets let you write down a seed phrase — usually 12 or 24 ordinary English words ("abandon amount bridge…"). Those words are your private key, expressed in a form a human can actually transcribe without typos. But they're more than one key: they're the seed from which many keys can grow.

The standard behind this is called BIP39. The words encode a big random number, and that number becomes the root of everything the wallet generates. Restore those same words into a compatible wallet and your addresses come back. Lose the words and the keys are gone forever — there is no password-reset flow, no "I forgot" button, no support ticket that can remake them.

Not every chain. BIP39 seeds cover Bitcoin, TEXITcoin, and most UTXO-style chains that share that family tree — and many EVM chains use the same seed standard too, so one phrase can restore Ethereum, USDC addresses, and more. But some chains use their own key scheme and a BIP39 seed won't restore them. Always check which seed format a specific chain expects before you assume one phrase rules them all.

So the seed phrase is powerful — but that power is exactly why you treat it like the most valuable object you own. Anyone with those words can regenerate every key that grows from them, on every compatible chain, and walk away with everything. Write it on paper or metal. Never photograph it, never text it, never type it into a random website that promises to "check" it for you.

3. HD wallets: one seed, infinite keys

"HD" stands for Hierarchical Deterministic, and it's the idea that turned seed phrases from "one key in disguise" into "a whole tree of keys." The standards are BIP32 and BIP44. Here's what they give you:

• Infinite addresses — From one seed, a wallet can generate a new address for every transaction without ever asking you for a new backup. The seed stays the master.
• Organised by purpose — Keys are arranged in a tree — coin type, account, change, address index — so different coins and different accounts live in their own branches.
• One backup, everything — Back up the seed once and you've backed up the entire tree. Restore it elsewhere and the same tree — same addresses, same keys — grows back identically.

Without HD wallets you'd have to back up every single address separately, and the moment you used a new one you'd risk losing track of it. HD makes "a wallet" feel like one thing while actually being a sprawling family of keys that all answer to the same seed. That's the magic — and it's also why losing the seed is so catastrophic.

The filing cabinet: derivation paths

An HD wallet's tree is navigated with a derivation path — a route like m/44'/0'/0'/0/0. Each number is a folder: 44 means "BIP44 standard," the next number is the coin (Bitcoin is 0, Litecoin is 2, TEXITcoin is 696969 — Bobby's idea, so it never collides with Litecoin or anything else, IskanderCoin is 969696, Ethereum is 60), then account, then change, then address index.

Why this matters: the same seed on the same wallet software always produces the same addresses, because it walks the same path. But a different wallet app might walk a different path by default — same seed, different addresses, and a moment of panic where your balance looks like zero. The coins aren't gone; the new app is just looking in a different folder. This is why "which derivation path does this wallet use?" is a real question, and why restoring into the same software (or one that matches its paths) is the safe move.

4. SegWit vs Legacy vs Native SegWit

This one shows up mostly on Bitcoin-family chains (and TEXITcoin inherits the family). It's about how an address is encoded, and it affects fees, compatibility, and what other software will accept. Three flavours:

• Legacy (P2PKH) — The original. Base58, starts with 1 (Bitcoin) or T (TEXITcoin). Universally supported — including the Omni Layer 2 that TSD rides on. Slightly higher fees, maximum compatibility.
• Nested SegWit (P2SH) — The "the other one." A SegWit transaction wrapped in a legacy address. Starts with 3. Cheaper than legacy, still accepted almost everywhere. A transitional format.
• Native SegWit (bech32) — The modern one. bech32 encoding: bc1… (Bitcoin) or txc1… (TEXITcoin). Cheapest fees, but some older services don't accept it — and the Omni Layer ignores it entirely.

Why it matters here: TSD (Texas Stable Dollar) is an Omni Layer token, and Omni reference outputs only recognise legacy base58 addresses — the ones starting with T. A txc1… bech32 address will silently fail to receive TSD. Same seed, same wallet, but the format you hand us has to be the one the receiving layer understands. That's not a wallet bug — it's a protocol rule.

5. Your seed unlocks a lot — if you know where to look

Because one seed can grow keys for many chains and many accounts, the seed alone isn't enough — you also need to know which branch the coins live on. It's like having a master key to a building but not knowing which floor or which room holds the thing you're after. The seed is the key; the derivation path and the coin type tell you the room.

Practical example: you restore your 12 words into a new wallet app and it shows an Ethereum balance of zero. Panic. But the balance is fine — the new app just defaulted to a different coin or path than your old one. You switch the app to the right coin, or tell it the right path, and the addresses — and the balance — reappear. The seed did its job; you just had to point it at the right drawer.

This is the single most common "where did my coins go?!" scare in all of crypto, and almost always the answer is "they're there, you're looking in the wrong branch." Keep a note of which wallet software you used and for which coin — it saves the detective work later.

6. Wallets do most of that work for you

The good news: you almost never deal with raw derivation paths or version bytes by hand. A wallet app picks the right path for the coin you selected, generates a fresh address from your seed when you need one, shows you the human-readable format, and hides the tree entirely. Your job is to:

1. Write the seed down — once, correctly, on paper or metal, before you fund anything.
2. Use the right address format — the wallet usually offers the correct one for the chain; you just have to paste it in the right field (TXC rewards, USDC commissions, etc.) on your profile.
3. Know which wallet and which coin — so a future restore lands on the right branch without a scavenger hunt.

The wallet is a guide through the key tree. The seed is the thing that matters when the guide is gone.

7. From a seed down to one specific key

Yes — your understanding is right. In an HD wallet, the seed generates a parent key, which generates child keys, which generate addresses. Each address has its own private key, and you can export the private key for one specific address without exposing the seed or any other address's key. It's a branch you can hand off without handing over the trunk.

This is exactly what happens when you import a Cold Storage Coin: that coin holds one private key for one address, laser-etched under the tamper seal. You scan it into a wallet and that single address — not your whole tree — comes alive. The wallet can then spend from that address because it now holds that one key. Your seed phrase (if you have one elsewhere) is untouched and unaware.

So the hierarchy, from broadest to narrowest, is:

seed phrase → master key → … coin / account / change / index → one private key → one public key → one address

You can stop at any level. Hand over the seed and you've handed over everything. Hand over one address's private key and you've handed over exactly that address's funds — nothing more. That granularity is genuinely useful, and it's why a single coin (one key, one address) can be carried in your pocket while your seed phrase stays in a safe.

8. Why moving from keys to seeds feels weird

If you started with the simple model — one public key, one private key, one address — then meeting the seed phrase for the first time is disorienting, and that's completely normal. Suddenly the thing you write down isn't "the key for this address" anymore; it's a master that silently generates keys for addresses you haven't even created yet, across coins you might not even be thinking about. The one-to-one relationship you learned first becomes one-to-many, and a lot of it is invisible until you need it.

The weirdness is real, but so is the convenience. The seed collapses an entire filing cabinet of keys into twelve words you can memorise. The trade-off is that those twelve words now carry the weight of every key in the cabinet — so the discipline around them has to match. Treat the seed like the master key to every drawer you own, because that's exactly what it is.

Once it clicks, the model is actually beautiful: one backup, infinite addresses, every coin in its own branch, and a single piece of paper (or metal) that survives every app, every device, and every reinstall — as long as you kept it safe and you know which branch to look in.

The rules that keep you sane

• The seed is everything. Every key, every address, every compatible coin — all of it. Back it up once, on paper or metal, before you fund.
• Never share a seed or private key. Not with us, not with support, not with anyone. We will never ask.
• Match the format to the chain. TXC legacy T… for TSD, EVM 0x… for USDC, the right prefix for each coin on your profile.
• Remember which wallet and which coin. It turns a future restore from a scavenger hunt into a routine copy-back.
• If a balance looks like zero after a restore, don't panic and don't move anything. You're probably just on the wrong branch — switch coins or paths in the wallet first.
• Test with a small amount first whenever you use a new address or a new format. Typos and wrong formats are the most expensive mistakes in crypto, and they're permanent.