Visual identity / September 2026
A little structure.
A lot of character.
An identity for a lab that works on what stays private. Precise geometry, an editorial pace, and one color used with intent.
Two gates.
One shared boundary.
PRIMARY LOCKUP
STANDALONE MARKThe mark forms a lowercase “m” from two offset gates. They share an upright, just as separate primitives can share a common account. The openings stay visible; the boundary is deliberate.
Use the orange mark with an ink wordmark on light backgrounds. Use the reversed wordmark on dark surfaces. Keep one stroke’s width of clear space around the mark, and use it at 24 pixels or larger.
Ink, paper,
a precise interruption.
#20221F#F7F8F6#F24B2B#ECEFE9#676D63Ink and paper do most of the work. Vermilion identifies the mark, primary actions, and a single point of interest. Use graphite for secondary text; keep essential reading in ink. Small orange text on paper uses the deeper tone #BE351A for legibility.
A clear voice.
A technical margin.
Privacy starts
at the account.
Use medium weight for headlines, regular for body copy, and generous line spacing where an idea needs room. Headlines are closely set, with no overlapping letters.
Aa Bb Cc Dd
0123456789
{ proof: valid }
The monospace belongs to circuit names, small labels, figure references, and code. It gives the technical detail a distinct place without turning every sentence into an interface.
Control the view.
Ribbed glass reveals an object selectively. Its edges stay exact, while the view through it changes. This material study connects the identity to the lab’s work on disclosure.
Keep the visual field quiet. Use fine rules, open layouts, and diagrams that explain an actual relationship. Motion is brief and purposeful: an entrance, an opening, a change of state. Respect reduced-motion settings.
Write from the work.
Say what happens.
Name the action, the information being proved, and the information that stays private. “The chain checks the threshold proof” gives a developer something to work with.
Let the detail carry the claim.
Explain the circuit’s actual boundary. Distinguish private witnesses from public inputs. Put qualifications beside the claim they qualify.
Keep a human rhythm.
Use connected sentences for explanations. Reserve short labels for navigation. Avoid rhetorical questions, inflated promises, repeated three-part slogans, and manufactured urgency.
Leave room for the reader.
Assume technical curiosity. Define unfamiliar terms where they matter. Invite people to inspect the implementation and form their own judgment.