A cryptocurrency interface can show a familiar token symbol and a polished logo without explaining which asset the reader is looking at. For designers, the useful distinction is between presentation information and the identifiers used by the application. Preparing an image improves its appearance; it does not establish the provenance of the token beside it.
Start with the token record
ERC-20 describes a standard interface for tokens on Ethereum. Its name and symbol methods are optional features intended to improve usability. The specification does not include a token-logo method. That observation is specific to this interface: applications may obtain artwork through other conventions, and other token systems may work differently.
A name, symbol or image should therefore not be treated as a uniqueness guarantee supplied by ERC-20. An application can keep the relevant network and contract address in its token record, while storing the artwork reference as a separate presentation field. A filename such as coin.svg identifies a file in a workflow, not the organization behind a token.
Prepare graphics separately
Consider a hypothetical interface with two token records that happen to use the same blue hexagon. Replacing one hexagon with a sharper drawing does not resolve the identity question. The data associated with each record still needs its own review. This separation also helps during a redesign: changing an icon should not silently change which token record a row represents.
For the artwork itself, begin with a source file that the project is entitled to use. Keep an original vector file when one exists. If the starting point is a raster image, cropping, resizing and tracing are preparation steps, not evidence of permission, affiliation or token authenticity. A cleaner outline cannot supply those missing facts.
Review the small version
Inspect the icon at the size used in the actual interface, as well as in an enlarged preview. A small gap or line that looks comfortable on a large canvas may become difficult to distinguish in a compact list. Compare the icon against both light and dark backgrounds and check its surrounding empty space. These are visual observations, not a security assessment.
Keep the exported artwork and a short handoff note together. Record its intended display size, background assumptions, source and version. When converting between raster and vector formats, compare the export with the input rather than assuming that a different file extension guarantees equivalent appearance.
Keep changes traceable
Artwork review and token-data review answer different questions. A useful change record identifies both the image that changed and the token record to which it belongs. If the same artwork is reused elsewhere, the record should make that relationship clear instead of relying on a recognizable symbol.
The result is a more understandable interface workflow: designers can improve legibility, while the application team checks the identifiers and data attached to the display. A recognizable logo remains helpful presentation information. It should not become a substitute for knowing what the interface is actually showing.
Technical reference
Fabian Vogelsteller and Vitalik Buterin, ERC-20 Token Standard, Ethereum Improvement Proposals, November 2015, sections name and symbol. The source was checked on 15 October 2026.
Author bio
Ethan Lee works on JPG to SVG, a free browser tool for local image preparation and SVG path tracing.