The shapes that carry value: a written amount, the several forms a wallet address takes, a recovery phrase, the identifier that comes back afterwards, and the text inside a payment code.
Nearly every other format on this reference fails loudly. A malformed host does not resolve, and you find out immediately. An armoured block with a broken fence will not open, and your software says so in words. A filename with a second extension hiding behind the first is visible the moment you widen the column. In each case the wrong shape announces itself, and the announcement is the finding.
This family behaves differently, and the difference is the reason it is written more tightly than the other four. A wallet address that is well formed and belongs to somebody other than the party you meant is not an error. It is a legal string. Software accepts it without hesitating, because there is nothing in it to object to. The failure is quiet, and once it has happened there is no ledger clerk to appeal to and no queue to join. That single property shapes every card below.
Loud failure and quiet failure
It is worth seeing the contrast set out plainly, because it explains why the eye checks in this family are worth the seconds they cost even though they settle so little.
| The wrong string | What happens next |
|---|---|
| A host with a character out of place | Nothing loads. You are told, before anything else happens. |
| An armoured block missing its blank line | Your software refuses the block and names the problem. |
| A filename padded out with spaces | The oddity is on screen as soon as the column is wide enough. |
| A wallet address for the wrong party | Accepted, in full, quietly, and with no way back. |
The last row is the whole reason this family exists. Everything above it can be caught after the fact. The last row cannot.
What a shape check does catch here
A format check is cheap and it catches a specific class of accident: a string that was clipped by a selection that stopped early, a string that picked up a stray character from the surrounding page, a string copied from the wrong line of a list, an address belonging to one chain pasted into a field expecting another, an amount that lost its separator on the way through a spreadsheet. These are ordinary mishaps of copying rather than plots, and they are common enough to be worth a few seconds.
Several shapes in this family also carry a checksum folded into the string itself. The older Bitcoin address form carries one in its tail. The newer form carries a longer one. A Monero address ends with one. The final word of a recovery phrase is constrained by one. That machinery means a single mistyped character usually produces a string that is rejected outright rather than a string that is quietly valid and points somewhere else. It is a guard against fingers.
What it is not is a guard against substitution. A checksum is computed from the rest of the string, so any complete address is consistent with itself. Replace one whole address with another whole address and the arithmetic still works. The check confirms the string is internally coherent; coherence and correctness are separate questions, and only the first one is visible on the page.
The shapes in this family
- An amount and its decimal placesWhere the separator sits, how many digits follow it, and what the system keeps instead
- A Bitcoin address in the older alphabetA mixed case run beginning 1 or 3, in the alphabet that leaves out four lookalike characters
- A Bitcoin address in the newer alphabetOpens bc1, stays in one case throughout, and uses a thirty two character body alphabet
- A Monero addressA fixed ninety five character run opening with 4, in the base58 alphabet
- A Monero subaddress and an integrated addressThree near identical strings separated by one character at the front and a total width
- A wallet seed phraseA fixed count of lower case words, single spaced, every one drawn from a fixed list
- A transaction idSixty four hexadecimal characters in one run, with no prefix and no separators
- What a payment QR code carriesA square code is a container; the shape worth reading is the text a scanner returns
What this family does not cover
No card here explains how to pay for anything, and none of them names a wallet, a service or a place to obtain one. There is no discussion of what a payment costs, what anything is worth, or what any figure has been recently. This reference publishes no rate, no balance, no confirmation count and no total of any kind. The only numbers on these pages are properties of the formats themselves: how many characters a string has, how many places sit to the right of a separator, how many words a phrase contains.
Nor does this family look anything up. Nothing on this site contacts a chain, a node or a scanner. An identifier printed here is a shape with the right number of characters and nothing behind it. Every example string in this family is a deliberate placeholder, either spelling out the word example or running a repeated letter, or counting up through the digits where the alphabet allows only digits. None of them would survive a checksum, which is intentional.
The question of who holds an address is outside every card in this family, permanently and by design. Format work cannot reach it. That boundary is the subject of what a shape proves, and the symptoms that bring people here are indexed at wrong shapes. If you have not read how a card is laid out, the six sections repeat in the same order on all eight pages below.