Every guide we have published, newest first. Search by title or filter by topic.
Step by step: getting your receive address from SSP, choosing the right network, checking the pasted address, sending a small test, and waiting for confirmations — plus the hiccups exchanges commonly throw at you.
Your wallet says insufficient funds while you hold hundreds in USDC. The reason is the difference between a chain's native coin and the tokens that live inside contracts — and why every transaction is paid for in the coin.
Many exchanges now publish a proof of reserves. What it genuinely proves about customer funds, the gaps it leaves open — self-reported liabilities, snapshots, borrowed coins — and how to read one critically.
Clipper malware watches what you copy and swaps crypto addresses for the attacker's at the moment you paste. How it works, how it gets installed, how to check addresses properly, and why confirming on a second device matters.
Kaspa lets parallel blocks count instead of discarding them, which is how a proof-of-work chain runs at ten blocks per second. How the blockDAG and GHOSTDAG work, why fees are measured in mass, and how Kaspa multisig vaults work.
Between pressing send and the first confirmation, your transaction sits in the mempool. What it is, how block producers pick transactions, why some get stuck, and why a pending transaction is public but not yet final.
Anyone can create a token, and some are built from the first line of code to extract money. How honeypots block sales, how rug pulls drain liquidity, the warning signs you can check, and what to do with tokens you never bought.
A message signature costs no gas and leaves nothing on-chain, but it binds your key to data. What login signatures prove, which off-chain signatures can move your funds, and how to read a signing request before you approve.
Someone who can threaten you in person doesn't need to break cryptography. Why wrench attacks are growing, why privacy is the best defence, what 2-of-2 multisig does and doesn't do against coercion, and how to structure holdings to reduce exposure.
Signatures decide who can spend; hash functions hold everything else together. What a hash is, where you meet one without noticing — txids, mining, addresses, the function selectors SSP decodes — and what hashes can't do.
A wrapped token is a claim, not the asset. Why WETH, WBTC and bridged tokens rest on completely different guarantees, why SSP's Polygon WBTC is a wrapper of a wrapper, and what to check before holding one.
When something goes wrong and you ask for help, scammers answer first. What fake support and recovery agents ask for, why legitimate support never cold-messages you, and what SSP support can and structurally cannot do.
Seed phrases and private keys can spend. An extended public key can only watch — but it watches everything in the account. How to tell which wallet material you're being asked for, and why 2-of-2 multisig changes what a single leaked seed is worth.
An unexpected token can't take anything from you — signing the claim can. The three things claim pages actually ask you to sign, why off-chain permits are the dangerous modern variant, and what SSP shows you for a typed-data signature.
A node decides what is true for you instead of repeating what a server said. What it actually buys — verification, privacy, unstoppable broadcast — what it really costs, and the honest gap between SSP letting you point at your own node and that being easy.
The relay never holds a key and cannot sign — but for fifteen minutes at a time it handles your xpub and your unsigned transaction. What the TTL indexes actually enforce, and why the wallet is built to distrust our own server.
A verification checkmark proves the source matches the bytecode — nothing more. Most contracts are proxies whose logic can be swapped after you approve them, which makes the real question who holds the upgrade key and whether there is a delay.
A real layer 2 inherits its security from the chain beneath it — and of the six EVM mainnets SSP supports, exactly one is a rollup. Why the same address across chains is a trap, and what a week-long withdrawal is actually buying you.
Short reorgs are routine, six confirmations is a Bitcoin-scale convention rather than a law, and depth only means something relative to what a block costs to produce. Why confirmations matter when receiving and barely at all when sending.
Attestations are not audits, USDC broke its peg because a bank failed, and the major fiat-backed stablecoins can freeze your address. What a stablecoin actually is, and the ten minutes of checking worth doing before you hold one.