Classical branding is built around a physical product, an office, a person at negotiations — there is time to convince a client through service and personal contact. A crypto project often does not have such a chance: the user makes a decision to trust or not trust a protocol in seconds, looking at the icon in the token list on an exchange. The logo here is not an element of decoration, but the only signal of trust at the moment when a person transfers real money into code that they cannot see or understand.
The second difference is the context of display. A corporate logo lives on a website, a signboard, a business card — everywhere there is space and control over the environment. A crypto logo competes for attention in a tight list of hundreds of tokens in a wallet, where next to it are the same round icons of competitors. The winner is not the one who is prettier, but the one who is distinguishable at the periphery of vision in a fraction of a second.
Color in crypto is not decoration, but a direct statement about the project's character. Top articles recommend 'blue for trust, orange for energy' — this is only half correct, because the choice of palette should stem from the positioning strategy, not abstract color psychology.
| Project strategy | Logic of color selection | Examples |
|---|---|---|
| Infrastructure (financial rails, institutional partners) | Blue, dark blue, neutral tones — signals of stability and predictability | Cardano #0033AD, Chainlink #375BD2, XRP #23292F |
| Speculative / disruptive (willingness to change market rules) | Rich, unconventional hues — a signal of courage and rejection of financial conservatism | Uniswap #FF007A (pink), Avalanche #E84142 (red) |
| Community-driven (community as the main asset) | Warm, 'human' colors with character, often unconventional combinations | Solana — gradient #9945FF → #14F195 |
Bitcoin breaks accessibility rules altogether: the contrast of its orange #F7931A on a white background is only 2,5:1, below any readability standards. But it is precisely this 'incorrectness' that became a trademark feature — the color is recognized at a glance because it looks like nothing else. This is an exception, not a recipe: replicating Bitcoin's trick deliberately is almost impossible, because recognizability was built over years of leadership, not designer boldness.
A simpler rule for a new project: choose one or two stable colors that align with the chosen strategy, and do not touch them for years. Distinctiveness from competitors is not achieved through the rarity of the hue, but through discipline in its use.
A logo for a crypto project must function at sizes 16×16, 24×24 and 32×32 pixels — that's exactly the scale at which it appears in wallets, on exchanges, and in blockchain explorers. This is a strict technical constraint, not a designer's recommendation for perfectionists.
Projects that skip this stage usually discover the problem ex post facto — when the community in Discord starts complaining that the token is 'not visible' in the list or gets confused with another asset.
Rebranding in crypto is not a redesign for 'freshness', but a strategic signal to the market about a change in positioning. A classic example is Stellar, which replaced a cartoon rocket with a strict geometric Saturn symbol. This is not an aesthetic decision: the project needed to look appropriate next to institutional partners like IBM World Wire, and the cartoon graphics hindered such trust.
Rebranding is justified in three cases: the project transitions from a speculative phase to an infrastructure phase (institutional partnerships are needed), the project expands into a multi-chain ecosystem (the old identity does not scale to sub-brands), or the previous visual was copied from a competitor and hinders differentiation. In all other cases, changing the logo without changing the strategy is a waste of budget and a risk of losing the recognizability accumulated over years of presence in wallet interfaces.
The key rule of safe rebranding is to preserve at least one recognizable element through the transition: color, form, or compositional principle. A sudden complete replacement of everything at once is perceived by the community as a sign of financial problems or team changes, even if that is not the case.
A project that releases tokens and products across multiple blockchains faces a challenge that traditional branding does not know: how to maintain identity unity with dozens of sub-brands. The solution is a modular system: one base palette, a unified set of icons, and clear combining rules, rather than individual designs for each product.
Bento builds its system using green and yellow as the colors of trust and exploration of new products — both shades are recognizable as belonging to one ecosystem, even when applied to different sub-brands. Namada uses a yellow-black palette with a dotted grid visually tied to the parent project Anoma — thus the child product inherits the parent's trust without literally copying it. This approach saves resources on each new launch and reduces the risk that a user won't recognize the connection between products of one ecosystem.
Classical branding is built around a physical product, an office, a person at negotiations — there is time to convince a client through service and personal contact. A crypto project often does not have such a chance: the user makes a decision to trust or not trust a protocol in seconds, looking at the icon in the token list on an exchange. The logo here is not an element of decoration, but the only signal of trust at the moment when a person transfers real money into code that they cannot see or understand.
The second difference is the context of display. A corporate logo lives on a website, a signboard, a business card — everywhere there is space and control over the environment. A crypto logo competes for attention in a tight list of hundreds of tokens in a wallet, where next to it are the same round icons of competitors. The winner is not the one who is prettier, but the one who is distinguishable at the periphery of vision in a fraction of a second.
Color in crypto is not decoration, but a direct statement about the project's character. Top articles recommend 'blue for trust, orange for energy' — this is only half correct, because the choice of palette should stem from the positioning strategy, not abstract color psychology.
| Project strategy | Logic of color selection | Examples |
|---|---|---|
| Infrastructure (financial rails, institutional partners) | Blue, dark blue, neutral tones — signals of stability and predictability | Cardano #0033AD, Chainlink #375BD2, XRP #23292F |
| Speculative / disruptive (willingness to change market rules) | Rich, unconventional hues — a signal of courage and rejection of financial conservatism | Uniswap #FF007A (pink), Avalanche #E84142 (red) |
| Community-driven (community as the main asset) | Warm, 'human' colors with character, often unconventional combinations | Solana — gradient #9945FF → #14F195 |
Bitcoin breaks accessibility rules altogether: the contrast of its orange #F7931A on a white background is only 2,5:1, below any readability standards. But it is precisely this 'incorrectness' that became a trademark feature — the color is recognized at a glance because it looks like nothing else. This is an exception, not a recipe: replicating Bitcoin's trick deliberately is almost impossible, because recognizability was built over years of leadership, not designer boldness.
A simpler rule for a new project: choose one or two stable colors that align with the chosen strategy, and do not touch them for years. Distinctiveness from competitors is not achieved through the rarity of the hue, but through discipline in its use.
A logo for a crypto project must function at sizes 16×16, 24×24 and 32×32 pixels — that's exactly the scale at which it appears in wallets, on exchanges, and in blockchain explorers. This is a strict technical constraint, not a designer's recommendation for perfectionists.
Projects that skip this stage usually discover the problem ex post facto — when the community in Discord starts complaining that the token is 'not visible' in the list or gets confused with another asset.
Rebranding in crypto is not a redesign for 'freshness', but a strategic signal to the market about a change in positioning. A classic example is Stellar, which replaced a cartoon rocket with a strict geometric Saturn symbol. This is not an aesthetic decision: the project needed to look appropriate next to institutional partners like IBM World Wire, and the cartoon graphics hindered such trust.
Rebranding is justified in three cases: the project transitions from a speculative phase to an infrastructure phase (institutional partnerships are needed), the project expands into a multi-chain ecosystem (the old identity does not scale to sub-brands), or the previous visual was copied from a competitor and hinders differentiation. In all other cases, changing the logo without changing the strategy is a waste of budget and a risk of losing the recognizability accumulated over years of presence in wallet interfaces.
The key rule of safe rebranding is to preserve at least one recognizable element through the transition: color, form, or compositional principle. A sudden complete replacement of everything at once is perceived by the community as a sign of financial problems or team changes, even if that is not the case.
A project that releases tokens and products across multiple blockchains faces a challenge that traditional branding does not know: how to maintain identity unity with dozens of sub-brands. The solution is a modular system: one base palette, a unified set of icons, and clear combining rules, rather than individual designs for each product.
Bento builds its system using green and yellow as the colors of trust and exploration of new products — both shades are recognizable as belonging to one ecosystem, even when applied to different sub-brands. Namada uses a yellow-black palette with a dotted grid visually tied to the parent project Anoma — thus the child product inherits the parent's trust without literally copying it. This approach saves resources on each new launch and reduces the risk that a user won't recognize the connection between products of one ecosystem.