Nostr WoT
Brand Assets

Brand guidelines & media kit

Nostr WoT brand assets for identity, signing and Lightning payments across compatible apps.

Brand guidelines for agents (Markdown)

Brand foundations

Nostr WoT brings identity, signing and Lightning payments together across compatible apps.

Audience

People managing their identity and payments, and developers connecting apps to signing, wallet and social-graph capabilities.

Character

Clear, approachable and precise. Make starting easy and keep permissions and next steps understandable.

Voice

Lead with the user’s action and explain its result. Name protocols where they help a developer make a decision.

“Review the signing request”

Use concrete actions instead of technical abstractions. Explain signing and payments separately; describe compatibility without promising support for every app.

🔧

Building an Integration?

Use these assets for Nostr WoT integrations involving signing, access or payments. Identify the capability your app supports. See our API documentation to get started.

Colors

Brand

Purple identifies Nostr WoT. Use the lighter purple for the symbol on dark surfaces. The wordmark stays near-black or white.

Actions

Primary actions use #4F46E5 with white text; hover uses #4338CA. Brand accents and action colors have different roles.

Status and ecosystem

Green, yellow and red describe distance or state; they never recolor our logo. Always add a label. Nostr purple belongs to the ecosystem identity, not a substitute product logo.

Dark Background#A5B4FC

Logo Only

Brand indigo#6366F1Logo and brand accents
Action indigo#4F46E5Primary buttons; hover #4338CA
Distance green#22C55EDirect follows (1 hop)
Distance yellow#EAB308Connections at 2 hops
Distance red#EF4444Connections at 3+ hops
Nostr Purple#8B5CF6Nostr branding

Typography

The wordmark uses fixed Inter Semibold vector outlines on every device. Page headings and body text use the native system font; code uses the monospace stack.

Use this hierarchy for the kit and comparable marketing layouts. Sizes are pixels at the default root size; the arrow shows the mobile-to-desktop change. Body text stays selectable and responsive. Keep the wordmark as its fixed SVG.

Type scale
RoleSize / line heightWeight
Page title36 / 40 → 48 / 48700
Section30 / 36700
Card20 / 28700
Body16 / 26400
Label14 / 20500
Headings

Your signer and wallet for Nostr

-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif
Body

Start easily, connect compatible apps and manage signing permissions and Lightning payments.

16px / 26px · 400
Code

await wot.getDistance(pubkey) // nostr-wot-sdk

"Fira Code", Consolas, Monaco, monospace

Imagery and iconography

Use the existing tactile indigo objects, pale lavender surfaces and fine orbit lines. Keep mint and coral accents restrained. Use genuine screenshots to demonstrate product UI; illustrations explain concepts.

Indigo objects on a pale lavender background.
Brand atmosphere: spacious, tactile and free of embedded text.
Developer-themed objects in the existing illustration style.
Developer content: use the matching asset rather than inventing a second visual style.

Interface icons

Reuse the shared icon family at 20–24 px in controls. Feature illustrations may be larger. Align icons optically with text; decorative icons are hidden from assistive technology and icon-only actions need a label.

Composition and motion

Build one clear focal point with aligned text and generous space. Keep copy and original vectors separate from imagery so they can be localized. Use subtle transitions and honor reduced motion. Essential content must remain visible without animation.

Interface in practice

Use these live examples to build recognizable, readable interfaces. Each example uses our shared website components.

Cards and content hierarchy

Give each card one purpose: a short heading, supporting information and an action when needed. Align padding across a row; allow text to wrap. Keep important information visible.

Card · default

Information card

Use the default card for settings summaries, explanatory content and grouped information. A plain card does not imply a click.

Card · interactive

A card with an action

Use the interactive treatment for a destination or next step. Provide a real link or button, a clear label and keyboard focus. Do not nest buttons inside a whole-card link.

Read the docs

Feature card

Use FeatureCard for a product capability: one icon, a short title and a concise explanation. Keep the icon decorative when the title supplies its meaning.

Card · gradient

Highlighted context

Use a subtle gradient for an introduction or callout. Keep ordinary content on neutral surfaces and reserve strong color for meaningful emphasis.

Actions and priority

Use one primary action per decision. Outline buttons support it; text links handle navigation. A pending action keeps its label, communicates progress and prevents repeat submission.

Badges and status

Use short, descriptive labels. State connection status or hop count explicitly; color does not certify trust. Badge examples here use neutral styling.

ConnectedNo connection

Forms and feedback

Keep labels visible above fields. Explain the expected input and place a specific error next to the field. Link help and errors for screen readers. These examples are read-only.

Example: a short name you can recognize.

Enter an account name.

Spacing and surfaces

Use a consistent rhythm within each component family. Stack columns on narrow screens and let translated text expand.

Card padding
16 px compact · 24 px standard · 32 px feature or spacious.
Grid gaps
24 px between cards; 32 px between larger content groups.
Corners
8 px controls · 12 px standard cards · 16 px feature cards.
Page width
1152 px maximum for marketing sections, with 24 px horizontal gutters.

Interaction and content states

Keyboard focus and themes

Keep focus visible on every action. Test light and dark surfaces, keyboard navigation, hover and disabled states. Do not use hover alone to reveal an essential action.

Expandable content

Use disclosures for optional detail, with a clear question or label. Keep essential instructions outside the collapsed area. This example uses the shared AccordionList.

Empty, loading and error states

Explain what is missing and offer a relevant next step. While loading, preserve context and announce progress. On error, keep user input and offer a specific recovery action.

Integration Examples

Describe integrations and social distance with clear labels.

Social distance

Show the number of follow links between accounts.

Connected (2 hops)
No path found

Hop Indicator

Display social distance with color coding.

1 hop2 hops3+ hops

"Powered by" Badge

Attribution for apps using WoT infrastructure.

Powered by Nostr WoT

Usage Guidelines

Do

  • • Use official colors and logos from this page
  • • Maintain adequate spacing around the logo
  • • Use the logo to indicate WoT integration
  • • Link back to nostrwot.com when possible
  • • Use for press coverage and articles

Don't

  • • Modify or distort the logo
  • • Use outdated or unofficial assets
  • • Imply official endorsement without permission
  • • Use in ways that misrepresent the project
  • • Place on busy backgrounds without contrast

Need Something Else?

For press inquiries, custom assets, or partnership discussions, get in touch with us.