Overview
Acid Privacy Ledger is a payments-infrastructure system that combines warm editorial calm with high-voltage financial signal. The design should feel trustworthy and infrastructural, but never old-bank conservative or generic crypto-neon.
Payy
Payy is the privacy-first stablecoin chain that can’t expose your transactions to the world.
3.0
12
Visits
Available Pages
Version History
Workflow Collections
Design Analysis
Payy Home design analysis
Acid Privacy Ledger is a payments-infrastructure system that combines warm editorial calm with high-voltage financial signal. The design should feel trustworthy and infrastructural, but never old-bank conservative or gen...
Image Direction
Use composited product screens, financial activity cards, tinted city or infrastructure imagery, and clean article pages with large serif headlines. Product visuals should feel rectilinear, layered, and purposeful, not decorative.
Colors
The system is anchored by deep navy and warm cream, with acid lime acting as the action and signal color. Large surfaces should remain either paper-cream or navy. Lime should appear as a sharp intervention, not a background theme.
Typography
Use a large editorial serif for hero and long-title moments, especially when explaining infrastructure at a human scale. Use Inter for everything operational: nav, button labels, body text, supporting metadata, and product UI.
Design.md
System Overview
Core identity and authoring metadata from the refto.one design model.
Acid Privacy Ledger
A privacy-finance marketing system built from warm paper space, deep navy product surfaces, acid-lime action signals, and large editorial serif headlines.
editorial fintech with privacy tension and sharp signal color
Primary mode: lightprivate payments infrastructure marketingproduct-marketing
Theme
Fields outside the primary renderer remain visible here as structured fallback content.
Visual atmosphere
Summary
editorial fintech with privacy tension and sharp signal color
Density
4
Variance
4
Motion
1
Signals
cream page field · navy ledger stage · acid-lime CTA · oversized serif hero
Colors
Primitive palettes and resolved token colors for the active preview mode.
Palette colors
Ledger Navy
#0A0F35
Paper Cream
#FBFAF6
Acid Lime
#D7FF00
Soft Divider
#D7D0C7
Ink Body
#171E3F
Card White
#FFFFFF
Usage rules
Keep the public-facing content warm and paper-like, not clinical white.
Reserve acid lime for action, state highlights, and select chart cues.
Use navy to carry the private-ledger product proof and financial seriousness.
Token Spacing
Spacing scales rendered as tokens with a simple length specimen.
xs
6px
sm
10px
md
16px
lg
24px
section
88px
Token Radii
Corner radii tokens with a live surface sample.
sm
0px
md
2px
lg
4px
full
999px
Typography Families
Font families from the current design YAML, including fallback stacks and usage character.
Display
Iowan Old Style
high-contrast editorial serif with financial gravitas
Body
Inter
clear modern UI and article body voice
Mono
Inter
operational UI labeling without a heavy code aesthetic
Typography Scale
Top-level typography scale rendered as live text specimens.
Display
clamp(3.8rem, 7vw, 6.4rem)/—
Display
H2
clamp(2rem, 4vw, 3.2rem)/—
H2
Body
1rem/—
Body
Caption
0.8125rem/—
Caption
Typography Rules
Fields outside the primary renderer remain visible here as structured fallback content.
Rules
Use the serif for hero and article-title moments only. · Use Inter for navigation, UI labels, and body copy. · Keep headings elegant but anchored by strong grid structure and contrast zones.
Motion
Motion tokens rendered as resolved values for timing and personality.
Duration
140ms-220ms
Easing
cubic-bezier(.2,.8,.2,1)
Spring
stiffness 100, damping 18
Motion
Resolved motion token values.
| Property | Value |
|---|---|
duration | 140ms-220ms |
easing | cubic-bezier(.2,.8,.2,1) |
spring | stiffness 100, damping 18 |
Layout Principles
Use strong split-screen or column contrast between editorial copy and ledger UI proof.
Let large serif copy breathe against the cream field.
Keep article pages generous, left-aligned, and rule-separated rather than card-heavy.
Component Preview
Low-complexity component tokens rendered as design-system specimens.
Buttons primary
Base Attributes
Background
#D7FF00
Text
#0A0F35
Border
0px none #D7FF00
Radius
0px
Padding
16px 28px
Min height
52px
Buttons secondary
Base Attributes
Background
#FBFAF6
Text
#0A0F35
Border
1px solid #171E3F
Radius
0px
Padding
16px 28px
Min height
52px
Buttons product toggle
Base Attributes
Background
#0A0F35
Text
#FFFFFF
Border
1px solid rgba(255,255,255,0.2)
Radius
0px
Padding
11px 20px
Min height
36px
Cards default
Feature Card
Component preview content
Base Attributes
Background
#FFFFFF
Text
#171E3F
Border
1px solid rgba(23,30,63,0.12)
Radius
0px
Padding
24px
Shadow
none
Cards ledger
Feature Card
Component preview content
Base Attributes
Background
#0A0F35
Text
#FFFFFF
Border
1px solid rgba(255,255,255,0.08)
Radius
0px
Padding
24px
Shadow
none
Navigation desktop
OverviewFeaturesDocs
Base Attributes
Background
transparent
Text
#171E3F
Height
44px
Active text
#171E3F
Item padding
0px 4px
Item radius
0px
Image direction
Schema-agnostic optional blocks from the design YAML. New option keys render here automatically.
Summary
Use split-view product compositions, finance dashboard crops, city or infrastructure photography in navy tints, and calm editorial blog layouts.
Guidance
- -Keep product proof rectilinear and layered, not soft or playful.
- -Use high-contrast compositions where the cream field and dark ledger stage directly confront each other.
Anti Patterns
Compact list of patterns the design system explicitly avoids.
- -No bubbly fintech pills or rounded-dashboard softness.
- -No bright rainbow crypto accents beyond the acid-lime signal.
- -No cold hospital white replacing the paper field.
- -No cute illustration systems fighting the editorial seriousness.