Transparent, non-custodial, yours

Reading an address well enough to not lose money

EVM addresses use mixed-case checksums; Solana uses base58. What each format catches, what it cannot, and why the same address works across EVM chains.

EVM format 0x plus 40 hex characters; capitalisation is a checksum
Solana format Base58, no prefix, usually 32–44 characters
Same address Valid across all EVM chains — which is the danger, not a feature

FBT Swap

What you should know

An address is a public identifier derived from a key. Getting one wrong is the most permanent mistake available in crypto, and the formats include safeguards precisely because of that.

Those safeguards catch typing errors. They do not catch sending to a correct address that belongs to the wrong person or the wrong chain, which is the error that actually costs people money.

EVM addresses and the capitalisation trick

An EVM address is twenty bytes shown as forty hexadecimal characters. The mixed capitalisation you see is not cosmetic — it encodes a checksum, so a wallet can detect a mistyped character that would otherwise look valid.

An all-lowercase address is still accepted by most tools, which means the check is skipped. Preferring the checksummed form is a free safety margin.

Why the same address works on many chains

Every EVM network derives addresses the same way, so one key produces the same address on Ethereum, BNB Chain, Polygon, Arbitrum and the rest. This is convenient and is also the source of the worst mistake in crypto.

The address being valid on the destination chain does not mean the token exists there or that anyone controls it there. Sending a token to a correct-looking address on the wrong network usually means it is gone.

Solana is a different format entirely

Solana addresses are base58-encoded 32-byte public keys — no 0x prefix, mixed case by nature, and typically 32 to 44 characters. An EVM address is not valid on Solana and vice versa.

Solana also has associated token accounts, so the address you send a token to is derived from your wallet address and the mint. Wallets handle this, but it is why a token balance can need an account created before it can be received.

Habits that prevent the permanent mistake

Verify the first and last several characters and at least one group in the middle — address poisoning attacks specifically target people who only check the ends. Send a small test amount for a first transfer to a new destination.

Confirm the network on both sides, every time. FBT Swap shows the selected network before each signature for exactly this reason.

At a glance

At a glance

EVM format

0x plus 40 hex characters; capitalisation is a checksum

Solana format

Base58, no prefix, usually 32–44 characters

Same address

Valid across all EVM chains — which is the danger, not a feature

Checksums catch

Typos only. Never a wrong but valid destination

FAQ

Frequently asked questions

Clear answers before you decide.

Can I recover tokens sent to the wrong network?

Sometimes, if you control the same address on the destination chain and the token exists there — you may be able to add it manually. If the address is a contract or an exchange deposit that does not support that chain, it is usually permanent.

Why do wallets reject an address that looks correct?

Usually a checksum failure from a single altered character, or a format mismatch — an EVM address pasted into a Solana field, for example. Both are the safeguard working.

Are ENS-style names safer?

They remove transcription errors but add a resolution step that can itself be attacked or expire. Verify the resolved address the first time you use a name, and treat a changed resolution as a reason to stop.

Risk notice

Crypto assets are volatile and on-chain transactions cannot be reversed. You can lose money, including all of it. Nothing here is financial advice.