gdb
[ DESIGN SYSTEM · WEB3 ] · 2025

Fhenix Design System

Cypher — the design system for Fhenix that makes confidential on-chain experiences (CoFHE) legible and consistent — tokens, components and patterns that bring clarity to complex cryptographic interactions.

Fhenix Design System — preview
PROBLEM

Confidential computing on-chain (FHE) is powerful but intimidating; each product screen risked reinventing patterns and drifting from brand.

APPROACH

A single token-based system — color, type, spacing, components and interaction patterns — documented and reusable across every Fhenix surface.

KEY DECISIONS

Accent-driven dark palette; Archivo + JetBrains Mono; reversible encrypt/decrypt states as a first-class pattern; progressive disclosure of cryptographic detail.

OUTCOME

A consistent, scalable foundation adopted across Fhenix product and brand.

OUTCOMES
NODES READ FROM .FIG
57,412
VARIABLES · 2 MODES
558
COMPONENTS · 14 SPECIMENS
9
THE HARD CALLS

Three decisions that shaped the product — what the alternative was, and what each choice cost.

01Accent as brand colour → STATE

Cyan is signal, never decoration

The obvious move is to paint the accent everywhere — buttons, headings, borders — so the product looks on-brand. In a confidential product that is dangerous: if cyan means "Fhenix" it cannot also mean "this value is encrypted". I reserved it for one job only, so a single glance at any screen tells you what is protected and what is exposed.

Cost: screens look quieter and less obviously branded than a competitor’s, and every new component has to justify using the accent at all — a rule the team has to police in review, forever.

02One humanist family → MONO

Monospace for every number

Two families is more to maintain than one. But encrypted balances change width as they resolve, and in a proportional face the digits jitter while amounts settle — which reads as instability in the exact moment a user needs to trust the number. Tabular mono keeps every figure on a fixed grid: values update without the layout twitching.

Cost: a second family to load and pair, and mono at small sizes is less comfortable to read — so it had to be strictly limited to data, never prose.

0316—24px, friendly → 4—12PX

Tight radii — instruments, not soft cards

Generous rounding is the current default and it reads as friendly and safe. This is financial cryptography: people are moving real value through an operation they cannot visually verify. Tight radii and a restrained elevation scale make the interface feel like an instrument that reports state, rather than a consumer app asking to be trusted on vibes.

Cost: it reads as colder and more expert-facing, which raises the bar for onboarding — a first-time user gets less visual reassurance and needs the copy to do that work instead.

PROCESS
Fhenix Design System — Five mechanical stages: decode the .fig binary, pull variables, normalise to tok
Five mechanical stages: decode the .fig binary, pull variables, normalise to tokens, build primitives, document.
Fhenix Design System — Five layers, one direction of dependency — a token never knows about a screen.
Five layers, one direction of dependency — a token never knows about a screen.
Fhenix Design System — Do / don’t principles that keep every Cypher-built dApp feeling like one product
Do / don’t principles that keep every Cypher-built dApp feeling like one product.
Fhenix Design System 1Fhenix Design System 2Fhenix Design System 3Fhenix Design System 4Fhenix Design System 5Fhenix Design System 6Fhenix Design System 7Fhenix Design System 8

Open in the interactive portfolio →

Have a product that deserves clearer design?

WRITE TO ME →

← Back to all work