Using SSP on Polygon, Base, and Other EVM Chains

A quiet strength of holding ETH in SSP is that the same setup reaches far beyond Ethereum. Polygon, Base, BNB Smart Chain, Avalanche C-Chain — these are all EVM chains, and your single SSP 2-of-2 multisig works across every one. No new wallet, no new key set, no second app to install. If you already understand Ethereum in SSP, you are most of the way to understanding all of them.

This guide explains the "same keys, different chain" story for anyone running an EVM wallet in self-custody: what "EVM-compatible" really means, how one key pair controls accounts on many chains, why each chain still needs its own gas token, the address question, and the pitfalls that trip people up. A good Polygon Base wallet self-custody setup makes multiple chains feel like one wallet — without losing track of what is actually separate underneath.

What "EVM-compatible" actually means

EVM stands for Ethereum Virtual Machine — the runtime that executes Ethereum's smart contracts. A chain is "EVM-compatible" when it runs that same virtual machine, or a faithful copy. In practice that gives you three things that matter for a wallet:

• The same execution model. Smart contracts written for Ethereum run on these chains with little or no change, and the account model, gas metering, and transaction format all behave the same way.
• The same address format. EVM addresses look identical everywhere — the familiar 0x... string of 40 hex characters. An address on Polygon looks exactly like one on Base or Ethereum.
• The same tooling. Wallets, explorers, and signing libraries that work on Ethereum work on every EVM chain, because the underlying machine is the same.

That shared foundation is why a single wallet can support many chains at once. The chains differ in who runs them, how fast and cheap they are, and which coin pays for gas — but the core machinery your wallet talks to is common to all.

One key set, every EVM chain

Because every EVM chain speaks the same language, SSP doesn't need a different design for each one. Your setup is still 2-of-2 multisig: key 1 in the SSP Wallet browser extension, key 2 in the SSP Key mobile app, with every transaction built in the extension and co-signed by a push approval on your phone. That model is identical whether you're on Ethereum, Polygon, Base, BNB Smart Chain, or Avalanche.

On EVM chains, SSP implements the 2-of-2 as an ERC-4337 smart-contract account that verifies a single Schnorr-aggregated signature — the two keys produce one combined signature the chain can check. The important part here is that the same key pair drives your accounts on every supported EVM chain. You aren't creating brand-new wallets when you start using Polygon or Base; you're pointing the wallet you already have at a different network.

The benefit is real: one backup protects all your EVM activity, and the guarantee that neither device alone can move funds holds on every chain. For the deeper mechanics, see EVM multisig: the account-abstraction way.

The address question: same address, deployed per chain

Here's a point worth getting exactly right, because it causes confusion. An ERC-4337 smart-account address is deterministic: it's computed in advance from your keys and the account's setup, typically using a mechanism called CREATE2 that calculates the address before the contract is even deployed. Because the inputs are the same on every EVM chain, the resulting address can be the same across Ethereum, Polygon, Base, and the others.

That's convenient — one address to recognize in many places — but it comes with a caveat. A smart-contract account only exists on a chain once it has been deployed (activated) there. Until then, there's no contract at that address on that chain, even though the math reserves it for you. SSP handles this deployment for you, usually when you make your first transaction on a new chain.

So hold both ideas at once: your address can be identical across EVM chains, but each chain keeps its own separate state. A balance on Polygon and a balance on Base are tracked independently, even at the same address. Same address, separate accounts — that distinction matters for everything below.

Each chain has its own gas token

Every EVM chain charges gas — a fee for the computation and storage your transaction uses — but each charges it in its own native coin. This trips up newcomers constantly, so it's worth being precise:

• Ethereum — gas is paid in ETH.
• Base — also paid in ETH (Base is an Ethereum L2 and uses ETH for gas).
• Polygon — gas is paid in POL (the token formerly known as MATIC).
• BNB Smart Chain — gas is paid in BNB.
• Avalanche C-Chain — gas is paid in AVAX.

The practical rule: to transact on a chain, you need a little of that chain's gas token in your account there. Holding a stablecoin on Polygon but no POL means you can't move it — there's nothing to pay the fee with. So keep a small gas buffer on each network you use. For how gas pricing works in depth — base fees, priority tips, and why costs swing with demand — read gas fees on Ethereum, explained for self-custody users.

Switching chains in SSP

Day to day, using another EVM chain is mostly a matter of telling SSP which network you want. In general terms, you select the chain in the wallet, and SSP shows that chain's accounts, balances, and the correct native gas token for fees. Sending and receiving then work just like on Ethereum — construct in the extension, approve on your phone, done.

Two things stay constant whichever chain you pick. First, the signing flow never changes: always two devices, one combined signature. Second, since your address may look the same across chains, the thing you actually choose — and must get right — is the network, not a different address.

L1 vs L2: where the cheaper chains fit

A useful mental model is the split between Layer 1 (L1) and Layer 2 (L2). Ethereum is an L1 — a base settlement layer that is secure and decentralized but can get expensive when busy. L2s like Base, and scaling networks like Polygon, handle transactions more cheaply and anchor their security back to a base layer. For most everyday transfers and app interactions, an L2 costs a fraction of what the same action costs on Ethereum L1.

That cost difference is the main reason people branch out from Ethereum to other EVM chains. You keep the same wallet and security model but pay far less per transaction. For a neutral overview of how these networks compare, L2BEAT tracks them in detail, and the Ethereum Foundation's Layer 2 page explains the framework. Just remember that "cheaper" doesn't mean "interchangeable" — which brings us to the pitfalls.

Common pitfalls to avoid

The flip side of one wallet reaching many chains is that it's easy to mix them up:

• Sending to the wrong network. Because addresses look identical across EVM chains, it's tempting to assume any 0x... address works anywhere. The format is the same, but funds land on whichever network the transaction is sent on. Send on the wrong chain — or to an exchange that only credits one specific network — and recovery can be difficult or impossible. Always confirm both the address and the network.
• Assuming a token on chain A is spendable on chain B. It isn't. USDC on Polygon is not the same balance as USDC on Base, even if the ticker matches. Each chain tracks its own balances (remember: same address, separate accounts). To use that value elsewhere, you have to bridge it — a separate operation that moves or re-issues the asset across networks, not a transfer to a different address. See bridging between EVM chains from SSP.
• Bridged and "wrapped" token confusion. When an asset crosses a bridge, what you receive is often a representation of the original — a wrapped or bridged token. Two versions of the "same" asset can even coexist on one chain if they came across different bridges, and they aren't interchangeable. Check that the token you hold is the one a given app actually expects.

None of this is unique to SSP — it's how the multi-chain EVM world works. SSP gives you one secure, two-device wallet across all of it; your job is to track which network you're on and what actually lives there.

Where to go next

If Ethereum itself still feels new, start with Ethereum in SSP, then come back here for the multi-chain picture. When you're ready to move value from one EVM chain to another, bridging between EVM chains from SSP walks through it carefully. And whenever fees surprise you, gas fees on Ethereum, explained for self-custody users covers what you're paying for. The throughline never changes: one key set, two devices, one signature — across every EVM chain SSP supports.