Tokens and addresses

Two pieces of reference data sit under every token card, and they are separate on purpose.

A token is the asset itself: its name, symbol, logo, whether it is a stablecoin, and where its price comes from. A token address is where that token lives on one specific chain: the contract address and its decimals.

USDC is one token with many addresses: one on Ethereum, one on Polygon, one on Arbitrum. Same asset, same price, different contracts.

Why the split matters

A token card needs the token and an address for the wallet's chain. A token that exists with no address on your chain still cannot be tracked there, which is the most common reason a card cannot be created.

Browsing tokens

Tokens in the sidebar lists every token SimplyLedger carries. Opening one shows its details, its addresses per chain, and its price history.

Three companion pages sit beside it:

Page	What it is for
Spam Tokens	Tokens marked as spam and excluded from reports. Removing one from spam brings it back into normal handling.
Token Requests	Requests for new tokens and new token addresses, waiting to be reviewed.
Fiat Tokens	The supported fiat currencies, used by fiat token cards on exchange wallets.

Native and contract addresses

An address is one of two types:

• Native: the chain's own coin: ETH on Ethereum, MATIC on Polygon. There is no contract, so the address is recorded as NATIVE and displayed as Native.
• Contract: everything else. The token's contract address on that chain.

Each address also carries an exponent, the token's decimals. It is what converts a raw on-chain amount into a human one, so a wrong exponent produces amounts that are wrong by orders of magnitude rather than slightly off. The address form has a Get decimals action that reads the value from the chain; use it rather than typing the number.

When something is missing

Gaps in this reference data surface on the posting overview, because that is where they stop work. A wallet lists them in the order they have to be fixed:

Flagged as	Meaning
Missing tokens	A transaction references a token SimplyLedger does not carry at all.
Missing token addresses	The token exists, but has no address on this chain.
Missing token cards	Token and address both exist; the wallet just has no card.

Each is resolved from that page, and the posting overview covers the actions on offer.

Most airdropped junk is genuinely spam. Marking it so keeps it out of the posting queue and out of reports, and it stays reversible from Spam Tokens.

Requesting a token or an address

Submitting a token or an address SimplyLedger does not already carry raises a request. Requests are listed under Token Requests, split into token requests and token address requests, and are usable once approved.

What each request needs:

Field	Notes
Token name and symbol	The full name and its ticker, for example Ethereum and ETH.
Price source	Where prices are fetched from. See token prices.
Source token ID	The token's identifier at that price source (ethereum for CoinGecko, not the symbol). Getting this wrong is what leaves a token with no prices.
Stablecoin	Tick when the token is pegged to a fiat currency.
Chain, address, exponent	For an address request: the chain, the contract address, and its decimals.

Who can submit

Creating tokens and addresses needs write access to the entity. Viewers and guests see the lists but not the actions. See roles and permissions.

Next

Token prices covers where the values shown against your balances and transactions come from, and how to fill a gap.