Github
EXOCHAIN FOUNDATION — Media Kit
Brand assets + guidelines for press, partners, community
Quick Start for Press
EXOCHAIN Foundation operates a constitutional trust fabric that enables verifiable identity adjudication, consent management, and evidence-grade finality for secure digital infrastructure. The protocol provides deterministic proof systems for custody, bailment, and compliance workflows across institutional and developer ecosystems.
Official Boilerplate (80 words)
EXOCHAIN Foundation maintains a proof-first trust infrastructure designed for identity adjudication, consent verification, and evidence-grade custody. Built on constitutional cybernetics principles, the protocol delivers deterministic finality through secure enclaves and merkle-DAG proof architectures. EXOCHAIN serves builders, compliance teams, institutions, and researchers requiring verifiable state transitions and constitutional guarantees. The Foundation operates with rigorous transparency, publishing open specifications and maintaining community-driven governance. All protocol operations prioritize security, auditability, and constitutional consistency over speculative value.
Approved Short Description: EXOCHAIN Foundation operates a constitutional trust fabric enabling verifiable identity, consent, and evidence-grade finality for secure digital infrastructure.
Logo Assets
Primary marks, wordmarks, lockups in PNG, SVG, EPS formats
Brand Guidelines
Complete specifications for colors, typography, spacing, usage
GitHub Repository
Canonical asset repository and version control

Critical: Use official assets only. Do not recreate, modify, or approximate the EXOCHAIN mark. Unauthorized alterations violate trademark guidelines and compromise brand integrity.
About EXOCHAIN
What It Is
EXOCHAIN Foundation operates a constitutional trust fabric—a proof-first infrastructure designed to establish verifiable state across identity, custody, and consent domains. Unlike traditional blockchain architectures optimized for asset speculation, EXOCHAIN prioritizes deterministic finality, evidence-grade auditability, and constitutional guarantees. The protocol implements secure enclave technology, merkle-DAG proof structures, and formal verification methods to ensure every state transition maintains cryptographic integrity.
What It Enables
The infrastructure supports four core capabilities: identity adjudication through cryptographic proofs, consent and bailment management with revocable permissions, evidence bundle generation for compliance and legal workflows, and deterministic finality that eliminates probabilistic settlement. These capabilities combine to create a trust layer suitable for high-stakes institutional operations, regulatory compliance, and systems requiring constitutional consistency rather than speculative value.
Who It Serves
  • Protocol Builders: Developers requiring verifiable state and deterministic outcomes
  • Security Teams: Organizations implementing custody, consent, and compliance frameworks
  • Institutions: Entities requiring evidence-grade audit trails and constitutional guarantees
  • Researchers: Academic and technical communities advancing formal verification methods
Asset Downloads
All brand assets are maintained in the official repository with semantic versioning and changelog documentation. Files follow consistent naming conventions for integration into press, partner, and community workflows. Download packages include multiple format options optimized for web, print, and digital media applications.
Download Media Kit
File Naming Conventions
All assets follow semantic naming patterns to ensure consistency and prevent versioning conflicts:
  • exochain-mark-primary.svg — Primary icon mark in full color
  • exochain-wordmark-white.png — Monochrome wordmark for dark backgrounds
  • exochain-lockup-horizontal.eps — Horizontal arrangement for print production
  • exochain-social-avatar-1024.png — Square profile image at optimal resolution
Logo System
The EXOCHAIN visual identity consists of five core configurations designed for flexibility across media contexts while maintaining constitutional precision. Each variant serves specific layout requirements and background conditions. Never modify, recreate, or approximate these marks—use only official assets from the approved repository.
1
Primary Mark
Icon-only configuration for compact applications, social avatars, and favicon usage. Maintains full recognizability at small scales.
2
Wordmark
Text-only configuration for headlines, editorial references, and contexts where the mark appears elsewhere on the page.
3
Horizontal Lockup
Combined mark and wordmark in horizontal arrangement. Preferred configuration for most applications including press releases and presentation headers.
4
Stacked Lockup
Vertical arrangement optimized for narrow layouts, mobile interfaces, and portrait-oriented compositions.
5
Monochrome Variants
Single-color versions (white or black) for use on photographic backgrounds, textured surfaces, or when color reproduction is limited.
Usage Rules
Always
  • Use official assets from approved repositories
  • Maintain original proportions and spacing
  • Ensure adequate contrast against backgrounds
  • Respect minimum size specifications
  • Apply clear space requirements consistently
Never
  • Stretch, skew, rotate, or distort any element
  • Add outlines, shadows, glows, or effects
  • Alter colors or substitute unauthorized palettes
  • Place on busy or low-contrast backgrounds
  • Recreate or approximate the mark from memory
Clear Space + Minimum Size
Proper spacing and sizing ensure the EXOCHAIN identity maintains visibility and impact across all applications. Clear space requirements prevent visual crowding and preserve the mark's constitutional precision. Minimum size specifications guarantee legibility in both digital and print contexts.
Clear Space Requirements
Clear space equals one times (1×) the mark's internal core unit—measured as the height of the primary geometric element within the icon. This exclusion zone must remain free of text, images, graphic elements, page edges, or other logos. Apply clear space consistently to all sides of any logo configuration.
For horizontal and stacked lockups, measure clear space from the outermost edge of the combined mark and wordmark. When positioning near page margins or content blocks, add an additional 0.5× core unit to prevent perceived crowding.
Minimum Size Specifications
Digital Applications:
  • Primary mark (icon only): 24px height minimum
  • Horizontal lockup: 120px width minimum
  • Stacked lockup: 80px width minimum
  • Wordmark: 100px width minimum
Print Applications:
  • Primary mark: 0.25 inches (6mm) height minimum
  • Horizontal lockup: 1.25 inches (32mm) width minimum
  • Stacked lockup: 0.75 inches (19mm) width minimum
  • Wordmark: 1.0 inch (25mm) width minimum
Do and Don't Examples
✓ Correct
Maintain original proportions, use approved colors, ensure adequate clear space, apply sufficient contrast
✗ Incorrect
Do not stretch horizontally, use unauthorized colors, crowd with other elements, or place on busy backgrounds
✓ Correct
Use monochrome variants on photographic backgrounds with proper clear space and contrast verification
✗ Incorrect
Do not add drop shadows, outlines, glows, gradients, or any visual effects to the mark
Color Palette
The EXOCHAIN color system balances constitutional authority with technical precision. The primary palette employs high-contrast combinations that ensure legibility across digital and print media while conveying the protocol's proof-first philosophy. Color specifications include values for all major reproduction systems to maintain consistency across production workflows.
Application Guidelines
Primary Accent
EXO Royal Purple serves as the primary brand accent. Use for interactive elements, call-to-action buttons, key data points, and visual emphasis. Purple dominates accent applications but should never overpower neutral foundations.
Highlight Color
EXO Gold functions as a secondary highlight for critical emphasis points. Apply sparingly—gold should appear in 10-15% of accent applications. Effective for success states, premium features, and selective data visualization.
Neutral Foundation
Night, Slate, and Cloud neutrals form the compositional foundation. Dark neutrals dominate backgrounds for maximum legibility. Maintain 70-80% neutral coverage in most layouts to ensure visual clarity and reduce cognitive load.
Accessibility Requirements
All color combinations must meet WCAG 2.1 Level AA contrast requirements (4.5:1 for body text, 3:1 for large text and UI elements). When applying EXO Royal Purple or EXO Gold, verify sufficient contrast against background colors. For critical text, default to high-contrast neutral combinations. Test all color applications with accessibility tools before publication.
Typography
The EXOCHAIN typographic system employs two carefully selected typeface families that balance technical precision with humanist accessibility. Inter serves as the primary workhorse for interface, editorial, and communication applications. JetBrains Mono handles code samples, technical proofs, and contexts requiring monospace precision. Both families support extensive international character sets and maintain excellent rendering quality across digital and print media.
Primary Typeface: Inter
Inter functions as the primary type family for all headings, body text, user interface elements, and general communication. Designed specifically for screen legibility, Inter's tall x-height and open apertures ensure clarity at small sizes. The family includes nine weights from Thin to Black, providing sufficient hierarchy options for complex information design.
Applications: Headlines, subheads, body copy, captions, user interface labels, navigation elements, callouts, pull quotes, data labels, table contents
Monospace Typeface: JetBrains Mono
JetBrains Mono serves specialized applications requiring fixed-width characters and enhanced code readability. The typeface features increased letter height, distinct character shapes, and ligature support for programming contexts. Use exclusively for technical content where character alignment matters.
Applications: Code snippets, command-line examples, hash values, cryptographic proofs, technical identifiers, API endpoints, JSON structures, formal specifications
Type Hierarchy
Fallback System
When Inter is unavailable, substitute SF Pro (Apple platforms) or Helvetica Neue (cross-platform). For JetBrains Mono, acceptable fallbacks include Menlo, Consolas, or Monaco. Always specify fallbacks in web font stacks and print specifications to ensure consistent rendering across environments.
Iconography + Diagram Style
EXOCHAIN visual communications employ a refined icon and diagram system rooted in blueprint aesthetics and technical precision. All visual elements maintain consistent stroke weights, geometric clarity, and minimal ornamentation. This approach reinforces the protocol's constitutional philosophy while ensuring clarity across scales and reproduction methods.
Line Icons Only
All icons use consistent 2px stroke weight with rounded caps and joins. Avoid filled shapes, gradients, or multi-weight combinations. Icons should read clearly at 24px minimum and scale without losing definition.
Blueprint Aesthetic
Diagrams employ thin-line technical drawing conventions. Use clean orthogonal or radial arrangements with minimal decorative elements. Arrows should be simple and directional without excessive flourish.
Approved Motifs
Merkle-DAG node structures, vault boundary representations, three-pillar constitutional symbols, and proof stamp geometric shapes form the core visual vocabulary. Apply consistently across materials.
Diagram Construction Principles
Structural Guidelines
  • Maintain consistent 2px line weight throughout diagrams
  • Use 8px grid for alignment and spacing precision
  • Apply rounded corners (2px radius) to rectangular containers
  • Employ directional arrows with 45° or 90° angles only
  • Label sparingly—diagrams should be largely self-evident
  • Group related elements using subtle container outlines
Color Application
  • Default diagrams to Night or Slate on light backgrounds
  • Apply EXO Royal Purple for active states or emphasis paths
  • Use EXO Gold sparingly for critical nodes or outcomes
  • Maintain neutral colors for 70% of diagram elements
  • Ensure all line colors meet WCAG AA contrast standards
  • Avoid gradients, shadows, or dimensional effects
Technical Motif Library
The following visual motifs represent core EXOCHAIN concepts and may be incorporated into diagrams, illustrations, and communications when contextually appropriate:
01
Merkle-DAG Nodes
Circular or hexagonal nodes connected by directional edges, representing cryptographic proof structures and state transitions
02
Vault Boundary
Rounded rectangular containers with secure-seal indicators, representing TEE (Trusted Execution Environment) isolation
03
Three Pillars
Vertical column arrangement symbolizing constitutional foundations: identity, consent, and custody
04
Proof Stamp
Geometric seal shapes (octagonal or circular) containing verification marks, representing deterministic finality
Imagery + Photography Direction
EXOCHAIN visual language employs abstract technical cinematography that conveys constitutional precision without resorting to cryptocurrency clichés. Imagery should evoke secure infrastructure, cryptographic proofs, and constitutional guarantees through sophisticated metaphor rather than literal representation. All photography and illustration must maintain the brand's premium minimal aesthetic while avoiding speculative or hype-driven visual tropes.
Preferred Visual Themes
  • Abstract Technical: Merkle-DAG lattices, node networks, proof structures rendered with cinematic lighting and minimal color palettes
  • Hardware Metaphors: Secure enclave representations, vault boundaries, TEE isolation concepts expressed through clean geometric forms
  • Constitutional Symbols: Three-pillar arrangements, seal structures, evidence containers that suggest authority and verification
  • Cinematic Minimalism: High-contrast compositions with dramatic lighting, heavy use of negative space, subtle purple/gold rim lighting
Avoid These Visual Tropes
  • Generic blockchain coins, token graphics, or cryptocurrency symbols
  • Stock "hacker in hoodie" photography or cyberpunk aesthetics
  • Cartoon robots, AI faces, or anthropomorphized technology
  • Neon gradients, glowing circuits, or Matrix-style green code rain
  • Charts with upward arrows suggesting price speculation
  • Literal padlock or key imagery (too simplistic for our context)
Visual Moodboard
Photography Art Direction
When commissioning or selecting photography for EXOCHAIN materials, apply the following technical specifications to maintain visual consistency:
Lighting
High-contrast dramatic lighting with single-source directionality. Employ rim lighting in purple or gold tones for accent. Avoid flat even lighting or multiple competing light sources.
Composition
Generous negative space with subject matter occupying 30-40% of frame. Use rule-of-thirds positioning. Maintain clean backgrounds free of clutter or competing elements.
Color Grading
Desaturated neutral base with selective color emphasis in purple/gold ranges. Target high contrast ratios. Blacks should be rich (RGB 11,11,15) rather than muddy gray.
Texture
Prefer matte surfaces, brushed metals, and subtle geometric textures. Avoid glossy plastics, organic patterns, or busy surface treatments that compete with content.
Brand Voice + Messaging
EXOCHAIN Foundation communications employ precise, constitutional language that conveys technical authority without hype or speculation. The voice balances accessibility for non-technical stakeholders with rigorous accuracy for protocol implementers and security researchers. Every message prioritizes verifiable claims, deterministic outcomes, and proof-first reasoning over aspirational promises or marketing superlatives.
Voice Attributes
Proof-First
Lead with verifiable evidence and deterministic outcomes. Support all claims with cryptographic, mathematical, or empirical foundations.
Constitutional
Reference foundational principles and governance structures. Emphasize systemic guarantees over individual opinions or market sentiment.
Calm Precision
Maintain measured tone without hyperbole. Avoid urgency-inducing language or speculative excitement. Communicate with deliberate clarity.
Non-Hype
Reject revolutionary rhetoric, guaranteed outcomes, or moonshot language. Focus on what exists and functions rather than what might be possible.
Language Guidelines
Preferred Terms
  • Verifiable (not "trustless")
  • Deterministic finality (not "instant" or "guaranteed")
  • Consent management (not "permissions")
  • Custody verification (not "ownership")
  • Evidence-grade (not "bulletproof")
  • Constitutional guarantees (not "promises")
  • Proof structures (not "blockchain")
  • Protocol specifications (not "whitepaper")
Avoid These Terms
  • Revolutionary, groundbreaking, paradigm-shifting
  • Guaranteed, unhackable, impossible to compromise
  • Moon, pump, get rich, financial returns
  • Trustless (implies distrust; use "verifiable")
  • Decentralized (overused; be specific about architecture)
  • Web3, crypto (generic; use precise protocol terms)
  • Game-changing, disruptive (empty marketing language)
  • Soon™, coming soon (uncertain timelines)
Core Messaging Framework
Tagline Options
  1. Constitutional Trust Infrastructure — Primary positioning emphasizing governance and systemic guarantees
  1. Verifiable State, Deterministic Outcomes — Technical positioning highlighting proof systems and finality
  1. Proof-First Protocol for Evidence-Grade Operations — Compliance positioning for institutional audiences
Elevator Pitch (1 Sentence)
EXOCHAIN Foundation operates a constitutional trust fabric enabling verifiable identity adjudication, consent management, and evidence-grade custody through deterministic proof systems and secure enclave architecture.
80-Word Boilerplate
EXOCHAIN Foundation maintains a proof-first trust infrastructure designed for identity adjudication, consent verification, and evidence-grade custody. Built on constitutional cybernetics principles, the protocol delivers deterministic finality through secure enclaves and merkle-DAG proof architectures. EXOCHAIN serves builders, compliance teams, institutions, and researchers requiring verifiable state transitions and constitutional guarantees. The Foundation operates with rigorous transparency, publishing open specifications and maintaining community-driven governance. All protocol operations prioritize security, auditability, and constitutional consistency over speculative value.
Key Messages (Non-Technical)
For general audiences, partners, and press communications, EXOCHAIN messaging emphasizes practical capabilities and real-world value without requiring deep technical expertise. These messages communicate what the protocol enables and why it matters to institutions, builders, and communities requiring verifiable digital infrastructure.
1
Verifiable Trust Without Speculation
EXOCHAIN provides constitutional guarantees for identity, consent, and custody operations without requiring participants to speculate on token values or market dynamics. The protocol focuses exclusively on verifiable state management and deterministic outcomes for high-stakes institutional workflows.
Supporting Evidence: Protocol economics separate operational functionality from speculative trading. All state transitions maintain cryptographic proofs independent of market conditions. Governance operates through constitutional mechanisms rather than token-weighted voting.
2
Evidence-Grade Auditability
Every state transition generates immutable proof bundles suitable for legal discovery, regulatory compliance, and institutional audit requirements. EXOCHAIN delivers forensic-quality evidence trails that meet the standards of financial services, healthcare, and government operations.
Supporting Evidence: Merkle-DAG proof structures provide cryptographic verification of all state changes. Secure enclave attestations guarantee execution integrity. Timestamp authorities ensure non-repudiable sequence ordering meeting legal discovery standards.
3
Constitutional Governance + Stability
Protocol rules are established through constitutional processes rather than ad-hoc decisions or majority-rule changes. This provides predictable operating conditions for institutions and builders requiring stable foundations for long-term infrastructure investments.
Supporting Evidence: Foundation operates under published constitutional framework with defined amendment procedures. Protocol specifications maintain backward compatibility commitments. Governance separates operations from speculation through multi-stakeholder consensus models.
Key Messages (Technical)
For protocol implementers, security researchers, and technical stakeholders, EXOCHAIN messaging emphasizes cryptographic foundations, formal verification methods, and architectural guarantees. These messages communicate how the protocol delivers deterministic finality and constitutional consistency at the implementation level.
Deterministic Finality Through TEE Architecture
EXOCHAIN employs Trusted Execution Environment (TEE) secure enclaves to eliminate probabilistic settlement and provide single-slot finality. All state transitions execute within attested environments that guarantee result determinism independent of network conditions or validator behavior.
Technical Proof Points: Intel SGX / ARM TrustZone attestation chains verify execution integrity. Remote attestation protocols enable third-party verification without trusted intermediaries. Enclave state transitions produce deterministic outputs provable through cryptographic commitments.
Merkle-DAG Proof Structures
The protocol implements directed acyclic graph (DAG) architectures with merkle commitments at each node, enabling efficient verification of historical state without requiring full chain replay. This structure supports selective disclosure and zero-knowledge proofs for privacy-preserving compliance.
Technical Proof Points: O(log n) verification complexity for historical state queries. Merkle path proofs enable light client implementations. DAG topology supports concurrent state transitions without global ordering requirements. ZK-SNARK integration provides verifiable computation without revealing transaction details.
Evidence Bundle Generation
Every protocol operation generates self-contained evidence bundles containing cryptographic proofs, attestation chains, and timestamp authorities. These bundles meet legal discovery standards and enable forensic reconstruction of state history for compliance and audit workflows.
Technical Proof Points: Evidence bundles include merkle proofs, enclave attestations, and RFC 3161 timestamps. Bundles remain verifiable independent of protocol liveness. Cryptographic commitments enable long-term archival with verifiability guarantees extending beyond current cryptographic assumptions through hash agility.
Usage Examples + Templates
EXOCHAIN provides production-ready templates for common communication contexts including press releases, presentations, social media, and email signatures. All templates incorporate proper logo usage, color specifications, typography hierarchy, and spacing requirements. These assets ensure consistent brand application across partner, press, and community touchpoints.
Press Release Header
Pre-formatted DOC and PDF templates with EXOCHAIN logo lockup, contact information blocks, and approved boilerplate placement. Includes clear space specifications and export settings for print-ready output.
Presentation Cover
PowerPoint and PDF slide templates with title placement, logo positioning, and background color specifications. Includes master slide layouts for section breaks and content slides.
Social Card Set
Pre-sized templates for 1:1 (Instagram/LinkedIn), 16:9 (Twitter/LinkedIn), and 9:16 (Instagram Stories) formats. Each includes safe zones, typography specifications, and approved background treatments.
Template Specifications
Layout + Safe Margin Specifications
All templates incorporate consistent margin and safe zone specifications to ensure proper rendering across devices and print production:
  • Print Materials: 0.5" (12.7mm) margins on all sides; 0.25" (6.35mm) bleed for full-bleed designs
  • Digital Documents: 48px margins on all sides for web display; 24px minimum for mobile optimization
  • Presentation Slides: 10% safe margin from edges (192px on 1920px width) to account for projection cropping
  • Social Cards: 80px margins on 1080px dimensions to prevent platform cropping on profile displays
  • Email Signatures: 16px padding within 600px container; ensure logo does not exceed 200px width
Press + Partner Guidance
Media professionals, journalists, and partner organizations should apply EXOCHAIN brand assets accurately and consistently. This section provides approved language, attribution requirements, and trademark usage guidelines to ensure proper representation of the Foundation and its protocol work across editorial and collaborative contexts.
How to Describe EXOCHAIN Accurately
When writing about EXOCHAIN Foundation or its protocol, use precise technical language that avoids cryptocurrency clichés and speculative framing. Preferred descriptions focus on verifiable capabilities rather than aspirational claims.
Approved: Protocol Description
"EXOCHAIN Foundation operates a constitutional trust infrastructure enabling verifiable identity adjudication, consent management, and evidence-grade custody through secure enclave architecture and merkle-DAG proof systems."
Approved: Technical Context
"The EXOCHAIN protocol provides deterministic finality for high-stakes institutional workflows requiring cryptographic proof of state transitions and constitutional governance guarantees."
Avoid: Speculative Framing
"EXOCHAIN is a revolutionary blockchain that will disrupt traditional finance and guarantee returns for early adopters." — This language misrepresents the protocol's purpose and introduces speculative claims.
Avoid: Generic Cryptocurrency Language
"EXOCHAIN is a decentralized crypto project launching a token for Web3 applications." — This fails to communicate the protocol's specific focus on constitutional trust infrastructure.
Attribution + Credit Requirements
Crediting the Foundation
When referencing EXOCHAIN in editorial contexts, use the full legal name on first mention: "EXOCHAIN Foundation." Subsequent references may use "EXOCHAIN" or "the Foundation." Always capitalize EXOCHAIN in all contexts—never lowercase or mixed case.
For technical specifications or protocol references, use "the EXOCHAIN protocol" or "EXOCHAIN infrastructure." Avoid possessive constructions that imply ownership claims ("EXOCHAIN's blockchain" → prefer "the EXOCHAIN protocol").
Source Attribution
When citing Foundation statements, specifications, or technical materials, attribute to "EXOCHAIN Foundation" with appropriate documentation links. Acceptable citation formats include:
  • "According to EXOCHAIN Foundation specifications..."
  • "EXOCHAIN Foundation documentation states..."
  • "As outlined in EXOCHAIN protocol whitepaper..."
Always link to canonical sources on exochain.foundation domain when citing technical claims or governance statements.
Trademark + Mark Usage Summary
EXOCHAIN and associated marks are trademarks of EXOCHAIN Foundation. The following usage guidelines apply to all external parties:
01
Editorial Use (Allowed)
Journalists and media may use EXOCHAIN marks in accurate editorial coverage without prior permission. Use official logo assets unmodified. Ensure coverage represents the Foundation's work accurately.
02
Partner Integration (Allowed with Guidelines)
Approved partners may use EXOCHAIN marks to indicate protocol integration or official collaboration. Must use "powered by EXOCHAIN" or "built on EXOCHAIN protocol" language. Contact brand team for approval.
03
Endorsement Implications (Not Allowed)
Do not use EXOCHAIN marks in ways suggesting Foundation endorsement of products, services, or organizations unless explicitly authorized. Do not create composite marks or modified versions.
04
Confusingly Similar Names (Not Allowed)
Do not use names, logos, or branding that could be confused with EXOCHAIN Foundation. Do not incorporate "EXOCHAIN" into your organization name without explicit licensing agreement.
Contact Information
Press Inquiries
Media relations, interview requests, statement requests
Brand + Partnership
Logo usage, partnership inquiries, trademark questions
Security Disclosures
Vulnerability reports, security research coordination
Email Signature Template
Standardized email signatures ensure consistent brand representation across Foundation communications. The template includes proper logo usage, contact hierarchy, and responsive formatting for cross-platform compatibility.
Signature Structure
Visual Layout
The signature uses a two-column structure with the EXOCHAIN mark in the left column and contact information in the right column. Maximum width: 600px to ensure compatibility with email clients. Logo should not exceed 80px height.
Use the monochrome mark (black or white depending on client background) to ensure rendering consistency. Avoid color logos in email signatures due to inconsistent client rendering.
Contact Information Hierarchy
  1. Name + Title: Full name in semibold, title in regular weight
  1. Organization: "EXOCHAIN Foundation" in regular weight
  1. Email: Active mailto: link in brand purple (#6700FF)
  1. Website: exochain.foundation as clickable link
  1. Optional: LinkedIn profile or relevant social link
Use Inter font family with 14px base size. Line height: 1.5. Color: #0B0B0F for primary text.
HTML Code Template
<table cellpadding="0" cellspacing="0" style="font-family: Inter, sans-serif; font-size: 14px; line-height: 1.5; color: #0B0B0F;">
  <tr>
    <td style="padding-right: 20px; vertical-align: top;">
      <img src="exochain-mark-monochrome.png" alt="EXOCHAIN" width="60" height="60" />
    </td>
    <td style="vertical-align: top;">
      <div style="font-weight: 600;">[Full Name]</div>
      <div>[Title]</div>
      <div>EXOCHAIN Foundation</div>
      <div><a href="mailto:[email]" style="color: #6700FF; text-decoration: none;">[email]</a></div>
      <div><a href="https://exochain.foundation" style="color: #6700FF; text-decoration: none;">exochain.foundation</a></div>
    </td>
  </tr>
</table>
Social Media Guidelines
EXOCHAIN social media presence maintains the brand's constitutional precision and proof-first philosophy across all platforms. Visual content, captions, and engagement strategies prioritize educational value and technical accuracy over viral engagement or speculative hype.
Platform-Specific Specifications
Profile Images
  • Recommended: Primary mark (icon only)
  • Dimensions: 1024 × 1024px
  • Format: PNG with transparency
  • Background: Transparent or solid Night (#0B0B0F)
  • Export: RGB color space, sRGB profile
Cover Images
  • Twitter: 1500 × 500px
  • LinkedIn: 1584 × 396px
  • Facebook: 820 × 312px
  • Safe zone: Center 1200 × 300px
  • Treatment: Abstract technical imagery with wordmark
Post Graphics
  • Square: 1080 × 1080px
  • Landscape: 1200 × 675px
  • Story: 1080 × 1920px
  • Margins: 80px safe zone
  • Typography: Inter, 48-72pt headlines
Content Voice + Tone
Social media content maintains EXOCHAIN's proof-first voice while adapting to platform conventions and audience expectations. Posts should educate, inform, and demonstrate technical credibility without resorting to engagement-bait tactics or speculative language.
1
Educational Focus
Explain protocol capabilities, technical architecture, and constitutional principles through clear examples and verifiable demonstrations.
2
Evidence-Based Claims
Support all assertions with cryptographic proofs, formal specifications, or published research. Link to documentation and technical resources.
3
Community Engagement
Respond to technical questions with precise answers and documentation links. Acknowledge contributions from researchers and implementers.
4
No Speculation
Avoid price discussion, market predictions, investment language, or any content that could be construed as financial advice.
Hashtag Strategy
Use technical and domain-specific hashtags that connect with protocol builders, security researchers, and institutional infrastructure teams. Avoid generic cryptocurrency hashtags that attract speculative audiences.
Primary Hashtags
  • #ConstitutionalCybernetics
  • #DeterministicFinality
  • #EvidenceGrade
  • #TrustedExecution
  • #MerkleDAG
  • #FormalVerification
Avoid These Hashtags
  • #Crypto #Blockchain (too generic)
  • #ToTheMoon #HODL (speculative)
  • #Web3 (overused, lacks specificity)
  • #Decentralized (prefer technical precision)
  • #DeFi (not applicable to protocol focus)
  • #Altcoin #Token (commodity framing)
Presentation Design Standards
EXOCHAIN presentations balance technical depth with visual clarity, employing consistent layouts that support complex information architecture while maintaining constitutional aesthetic principles. Slide design prioritizes hierarchy, generous whitespace, and strategic use of visual elements to guide audience attention.
Slide Layout Principles
Hierarchy Through Scale
Use dramatic size differences between headline and body text (3:1 minimum ratio). Headlines should dominate visual field, with supporting content clearly subordinate.
Generous Whitespace
Target 40-50% whitespace per slide. Resist temptation to fill empty space. Negative space directs focus and prevents cognitive overload.
One Idea Per Slide
Each slide should communicate a single core concept. Complex topics span multiple slides rather than crowding one slide with competing messages.
Master Slide Templates
Typography in Presentations
Size Hierarchy
  • H1 (Title Slides): 72pt, Bold
  • H2 (Section Headers): 48pt, Semibold
  • H3 (Subheads): 36pt, Semibold
  • Body Text: 24-28pt, Regular
  • Captions: 18-20pt, Regular
  • Code/Data: 20-24pt, JetBrains Mono
Application Rules
  • Never use text smaller than 18pt—if it doesn't fit, split the slide
  • Limit body text to 6-7 lines per slide maximum
  • Use sentence case for headlines (not ALL CAPS)
  • Maintain 1.3-1.5 line height for readability
  • Left-align body text; center headlines selectively
  • Apply consistent weight hierarchy within each slide
Color Application in Slides
Default to dark backgrounds (Night #0B0B0F or Slate #1A1A1F) with light text for reduced eye strain during extended presentations. Reserve light backgrounds for print handouts or documents requiring annotation. Apply EXO Royal Purple (#6700FF) and EXO Gold (#FFD700) sparingly—use for 10-15% of visual emphasis, never for body text.
Print Design Specifications
EXOCHAIN print materials maintain digital brand standards while accommodating production requirements for offset printing, digital printing, and large-format output. All print specifications include CMYK color conversions, bleed requirements, and paper stock recommendations to ensure consistent reproduction quality.
Color Specifications for Print

Rich Black Note: Night (#0B0B0F) uses 94% black plus CMY support colors. This produces deep, saturated blacks but requires careful press management to avoid over-inking. For text-heavy documents, consider using 100% K (single-color black) for body text with rich black reserved for solid areas.
Paper Stock Recommendations
Premium Documents
Stock: 100lb Gloss Text or 80lb Silk Cover
Finish: Gloss or Satin
Use: Annual reports, investor materials, brand guidelines
Note: Gloss stocks maximize purple/gold saturation
Business Collateral
Stock: 80lb Matte Text or 14pt Uncoated Cover
Finish: Matte or Uncoated
Use: Stationery, business cards, promotional materials
Note: Uncoated stocks require adjusted CMYK values
Technical Documentation
Stock: 70lb Offset Text or 24lb Bond
Finish: Uncoated
Use: Specifications, whitepapers, internal documents
Note: Optimize for readability over color accuracy
Bleed + Margin Specifications
Standard Document Sizes
  • US Letter: 8.5" × 11" + 0.125" bleed
  • A4: 210mm × 297mm + 3mm bleed
  • Business Card: 3.5" × 2" + 0.125" bleed
  • Poster (Small): 18" × 24" + 0.25" bleed
  • Poster (Large): 24" × 36" + 0.5" bleed
Safe Zones + Margins
  • Letter/A4: 0.5" (12.7mm) minimum margin
  • Business Cards: 0.125" (3mm) safe zone
  • Posters: 1" (25mm) minimum margin
  • Bound Documents: Add 0.25" gutter to binding edge
  • Logo Clear Space: 1× core unit from page edges
File Preparation for Print
All print files should be prepared using the following specifications to ensure proper reproduction:
  • Color Mode: CMYK (convert from RGB using Adobe profiles: US Web Coated SWOP v2)
  • Resolution: 300 DPI minimum for raster images; vector elements preferred
  • Fonts: Outline all fonts or embed with full character sets
  • File Format: PDF/X-1a:2001 or PDF/X-4:2010 for professional printing
  • Overprint: Set rich black elements to overprint, avoid overprint on small text
  • Transparency: Flatten all transparency before final output
Website Design Standards
EXOCHAIN digital properties employ responsive design principles with mobile-first considerations and performance optimization. Website design balances constitutional aesthetics with functional requirements for documentation browsing, GitHub integration, and technical resource access.
Layout + Grid System
Desktop Specifications
  • Max Width: 1440px content container
  • Grid: 12-column system with 24px gutters
  • Margins: 80px horizontal margins at max width
  • Breakpoints: 1440px, 1024px, 768px, 375px
  • Typography: 18px base font size, 1.6 line height
  • Spacing: 8px base unit, multiples of 8 for all spacing
Mobile Specifications
  • Base Width: 375px (iPhone standard)
  • Margins: 16px horizontal margins
  • Touch Targets: 44px minimum tap area
  • Typography: 16px base font size, 1.5 line height
  • Navigation: Hamburger menu below 768px
  • Images: Lazy loading, responsive srcset
Navigation Architecture
Primary navigation maintains consistent positioning and hierarchy across all pages. Top-level navigation should contain 5-7 items maximum. Use mega-menus for complex hierarchies, dropdown menus for simple hierarchies.
01
Global Header
Fixed position header with EXOCHAIN horizontal lockup (left), primary navigation (center), and CTA button (right). Height: 80px desktop, 64px mobile.
02
Primary Navigation
Protocol, Documentation, Research, Community, Foundation. Each section includes 3-5 sub-pages accessible via hover (desktop) or tap (mobile).
03
Utility Navigation
Secondary links in header or footer: GitHub, Contact, Press Kit, Careers. Use outline button style for CTAs like "Read Docs" or "Get Started".
04
Footer Navigation
Multi-column footer with grouped links: Protocol sections, Community resources, Foundation info, Legal/Privacy. Include social icons and contact email.
Component Specifications
Accessibility Requirements
All website components must meet WCAG 2.1 Level AA standards. Critical accessibility considerations include:
  • Color Contrast: Minimum 4.5:1 for body text, 3:1 for large text and UI elements
  • Keyboard Navigation: All interactive elements accessible via keyboard with visible focus states
  • Screen Readers: Semantic HTML5, ARIA labels where needed, skip navigation links
  • Forms: Clear labels, error messaging, validation states with text + color cues
  • Media: Alt text for images, captions for video, transcripts for audio content
  • Responsive Text: Text scales with browser zoom up to 200% without breaking layouts
Video + Motion Design
EXOCHAIN motion design employs subtle, purposeful animation that supports user comprehension without introducing visual noise or distracting flourishes. All motion follows consistent timing curves and respects user preferences for reduced motion. Video content maintains brand aesthetic with careful consideration for technical accuracy and educational value.
Animation Principles
Purposeful Timing
Duration: 200-400ms for UI transitions, 600-1000ms for content reveals. Use ease-out curves for entrances, ease-in for exits. Never exceed 1000ms except for complex data visualizations.
Layered Sequencing
Stagger related elements by 50-100ms to create rhythm. Animate groups as cohesive units. Use parent-child relationships where appropriate (container first, then contents).
Reduced Motion
Respect prefers-reduced-motion media query. Provide instant state changes for users who have enabled reduced motion preferences. Never rely solely on motion to convey information.
Video Specifications
Technical Specifications
  • Resolution: 1920 × 1080px (1080p) minimum, 4K for premium content
  • Frame Rate: 30fps standard, 60fps for data visualizations
  • Codec: H.264 for web, ProRes for archival/source files
  • Bitrate: 8-12 Mbps for 1080p web delivery
  • Aspect Ratio: 16:9 standard, 1:1 for social, 9:16 for stories
  • Audio: 48kHz, stereo, -14 LUFS target loudness
Production Standards
  • Typography: Minimum 48pt text size for readability
  • Safe Zones: Keep critical content within 10% margins
  • Pacing: 3-5 second minimum per information segment
  • Captions: Always include burned-in or sidecar SRT captions
  • Branding: Include logo lockup in intro/outro (3-5 seconds)
  • Length: 60-90 seconds optimal for social, 3-5 minutes for technical deep-dives
Motion Design Toolkit
Approved animation patterns for UI and video content:
1
Fade + Scale
Entrance: opacity 0→1 with scale 0.95→1.0 over 300ms ease-out. Creates subtle depth without dramatic movement.
2
Slide + Fade
Content reveal: opacity 0→1 with 24px vertical slide over 400ms ease-out. Use for cards, sections, modal overlays.
3
Stagger Sequence
List items: 100ms delay between items, fade + slide entrance. Maximum 8-10 items before eliminating stagger to prevent excessive duration.
4
Loading States
Pulse animation: opacity 0.3→1.0 over 1200ms ease-in-out infinite. Use for skeleton screens and loading indicators.
Video Content Guidelines
EXOCHAIN video content prioritizes technical education over promotional messaging. All videos should demonstrate protocol capabilities, explain architectural decisions, or provide implementation guidance. Avoid generic hype content, market speculation, or entertainment-focused material that doesn't serve educational objectives.
Community + Developer Assets
EXOCHAIN provides community-focused brand assets enabling builders, contributors, and community members to create accurate representations of protocol work. These assets balance accessibility with brand consistency, empowering community creativity while maintaining constitutional precision.
Community Asset Package
Badges + Stickers
Downloadable badge graphics for "Powered by EXOCHAIN", "Built on EXOCHAIN Protocol", and "EXOCHAIN Verified" use cases. Includes size variants and usage guidelines. SVG and PNG formats provided.
Social Templates
Pre-formatted templates for announcing integrations, sharing technical milestones, and highlighting protocol features. Includes Figma source files for customization within brand parameters.
Slide Deck Templates
Community presentation templates for meetups, hackathons, and educational events. Includes title slides, content layouts, and technical diagram templates with proper EXOCHAIN attribution.
Developer Branding Guidelines
Integration Badges
When building on EXOCHAIN protocol, use approved integration language and badge graphics:
  • "Powered by EXOCHAIN" — For applications using EXOCHAIN as core infrastructure
  • "Built on EXOCHAIN Protocol" — For projects implementing EXOCHAIN specifications
  • "EXOCHAIN Compatible" — For tools and services supporting EXOCHAIN integrations
Badges should link to exochain.foundation and appear in footers, about pages, or technical documentation.
Attribution Requirements
Open-source projects and community implementations should include attribution in documentation:
  • Include "Built on EXOCHAIN Protocol" in README files
  • Link to official documentation and specifications
  • Cite specific protocol components used (e.g., "identity adjudication", "merkle-DAG proofs")
  • Use code comments for technical integrations
  • Respect MIT/Apache licensing where applicable
Community Content Guidelines
Community members creating EXOCHAIN-related content (blog posts, tutorials, videos, social media) should follow these guidelines to maintain accuracy and brand integrity:
1
Accurate Technical Representation
Describe protocol capabilities accurately using approved terminology. Avoid speculation about future features or unofficial roadmap claims. Link to official documentation for technical details.
2
No Endorsement Implications
Do not suggest EXOCHAIN Foundation endorses your project, service, or content unless you have written approval. Use "community member" or "protocol builder" attribution rather than implying official status.
3
Brand Asset Usage
Use official logos from the media kit unmodified. Do not create custom variations or incorporate EXOCHAIN marks into your own branding. Maintain clear visual separation between Foundation assets and community content.
4
Educational Focus
Prioritize technical education and protocol understanding over promotional messaging. Avoid hype language, price speculation, or investment-focused content. Contribute to knowledge base, not market noise.
Partnership + Co-Branding
EXOCHAIN Foundation collaborates with research institutions, protocol implementers, and infrastructure partners on joint initiatives requiring co-branded materials. Partnership branding maintains both organizations' visual identities while clearly communicating the collaborative relationship and respective contributions.
Co-Branding Hierarchy
Equal Partnership
When organizations contribute equally to an initiative, use horizontal logo lockups with equal sizing and neutral separation. Alphabetical ordering or contribution-based positioning both acceptable. Maintain minimum clear space for both logos.
Example applications: Joint research publications, co-hosted events, collaborative protocol specifications
Primary/Secondary Partnership
When EXOCHAIN serves as primary infrastructure provider or lead organization, position EXOCHAIN lockup first (left) at 1.2-1.5× the size of partner logo. Use "powered by" or "in collaboration with" descriptor text.
Example applications: Integration partnerships, sponsored research, infrastructure implementations
Partnership Badge System
1
Research Partner
For academic institutions and research organizations conducting EXOCHAIN-related research. Badge includes university logo with "EXOCHAIN Research Partner" designation. Requires active research collaboration agreement.
2
Implementation Partner
For organizations building production systems on EXOCHAIN protocol. Badge indicates technical integration and Foundation support relationship. Requires verified protocol integration and partnership agreement.
3
Infrastructure Partner
For hosting providers, security auditors, and technical service providers supporting EXOCHAIN operations. Badge acknowledges operational contribution to protocol ecosystem. Requires active service agreement.
Joint Material Requirements
Co-branded materials must meet both organizations' brand standards while maintaining clear attribution and visual balance:
  • Logo Treatment: Both logos appear unmodified in approved colorways with proper clear space
  • Color Palette: Either organization's colors acceptable; avoid creating custom "blended" palettes
  • Typography: Use EXOCHAIN typography standards unless partner requires their typeface
  • Attribution: Include clear descriptions of each organization's role and contribution
  • Approval: Both organizations must approve final materials before publication
  • Usage Rights: Define intellectual property ownership and usage rights in partnership agreement
Co-Branding Review Process
All co-branded materials require Foundation review before publication. Submit materials to brand@exochain.foundation at least 10 business days before intended publication date. Include:
  1. Draft materials in native format (Figma, InDesign, Keynote, etc.)
  1. Partnership context and intended distribution channels
  1. Both organizations' brand guidelines for reference
  1. Timeline for review, revisions, and final approval
  1. Distribution plan (print quantities, web publication date, event details)
International + Localization Guidelines
EXOCHAIN brand maintains consistency across languages and international markets while respecting cultural contexts and localization requirements. Visual identity elements remain universal, while text content adapts to regional languages following consistent translation principles and technical accuracy standards.
Logo + Visual Elements
EXOCHAIN visual identity does not localize. The mark, wordmark, and lockups remain unchanged across all markets. Never translate "EXOCHAIN" into other languages or create localized logo variants. The brand name functions as a universal identifier independent of language context.
✓ Correct: Universal Logo
Use standard EXOCHAIN horizontal lockup in all materials regardless of language. The mark and wordmark appear exactly as specified in English-language guidelines.
✗ Incorrect: Translated Logo
Do not create localized versions like "エクソチェーン" or "异链基金会". Do not transliterate the brand name or create phonetic equivalents in non-Latin scripts.
Typography for International Content
Latin Script Languages
Continue using Inter for all Latin-script languages (English, Spanish, French, German, Portuguese, etc.). Inter includes extensive character set coverage for European languages including diacriticals and special characters.
Fallback: If Inter lacks specific glyphs, substitute system defaults while maintaining size and weight hierarchy.
Non-Latin Scripts
For languages using non-Latin scripts, substitute culturally appropriate typefaces with similar characteristics:
  • Chinese: Noto Sans CJK SC/TC, Source Han Sans
  • Japanese: Noto Sans CJK JP, Hiragino Sans
  • Korean: Noto Sans CJK KR, Apple SD Gothic Neo
  • Arabic: Noto Sans Arabic, Tajawal
  • Cyrillic: Inter (includes Cyrillic), PT Sans
Translation Principles
When translating EXOCHAIN content into other languages, maintain technical accuracy and constitutional tone while adapting to linguistic conventions:
01
Technical Accuracy First
Preserve precise technical meaning over stylistic flourish. Cryptographic terms, protocol names, and architectural concepts should translate literally or remain in English when no accurate equivalent exists.
02
Constitutional Tone
Maintain formal, authoritative register appropriate to constitutional language in target culture. Avoid casual or colloquial translations that undermine protocol seriousness.
03
Cultural Adaptation
Adapt examples, metaphors, and contextual references to resonate with local audiences while preserving core message. Replace region-specific references with culturally relevant equivalents.
04
Glossary Consistency
Maintain translation glossary for technical terms to ensure consistency across materials. Key terms like "deterministic finality" should translate identically in all content.
Market-Specific Considerations
Event + Conference Branding
EXOCHAIN presence at conferences, meetups, and technical events maintains brand consistency while adapting to diverse event formats and venue constraints. Event materials balance visibility with constitutional precision, ensuring protocol representation aligns with technical credibility rather than promotional excess.
Conference Booth Design
Backdrop + Signage
Primary backdrop: 10' × 8' fabric display with EXOCHAIN horizontal lockup centered. Dark background (Night or Slate) with subtle abstract technical imagery. Avoid busy graphics that compete with logo visibility.
Collateral Display
Literature rack with protocol specification printouts, one-page technical overviews, and media kit cards. Business card holder with team cards. Avoid promotional swag that doesn't serve technical education.
Demo Stations
Laptop stations running protocol demonstrations with large monitors (32" minimum). Display technical architecture diagrams, proof visualizations, and evidence bundle generation workflows. Include QR codes linking to documentation.
Event Collateral
Essential Materials
  • One-Sheet: Single-page protocol overview with QR code linking to full documentation (8.5" × 11", double-sided)
  • Business Cards: Team member cards with name, title, email, website (3.5" × 2", premium matte stock)
  • Stickers: EXOCHAIN mark die-cut stickers for laptop placement (3" diameter, weatherproof vinyl)
  • Banners: Retractable banner stands for booth corners (33" × 80", fabric or vinyl)
Optional Materials
  • Technical Poster: Large-format architecture diagram for wall mounting (24" × 36", matte poster stock)
  • Specification Booklet: Multi-page protocol specification digest (8.5" × 11", saddle-stitched, 16-24 pages)
  • Demo Cards: Wallet-sized cards with demo URLs and access credentials (2" × 3.5")
  • Team Badges: Custom name badges with EXOCHAIN branding for recognizability
Presentation + Speaking Engagements
When representing EXOCHAIN at conferences or technical talks, use approved presentation templates with the following guidelines:
1
Opening Slide
Title slide with talk title, speaker name/title, EXOCHAIN lockup. Include event name and date. Use full-bleed abstract technical image as background with text overlay.
2
Content Delivery
Balance technical depth with visual clarity. Use diagrams and architecture visualizations liberally. Include code examples in JetBrains Mono. Maintain consistent header positioning across slides.
3
Closing Slide
Thank you slide with contact information, documentation links, GitHub repository, and QR code. Include EXOCHAIN lockup and "Questions?" prompt.
Virtual Event Specifications
For virtual conferences and online presentations, adapt event branding for digital delivery:
  • Virtual Background: 1920 × 1080px Zoom/Teams background with subtle EXOCHAIN branding (logo in corner, abstract technical texture)
  • Lower Third: Name + title overlay template for video presentations (1920 × 200px, semi-transparent slate background)
  • Screen Share Template: PowerPoint/Keynote slides optimized for 1920 × 1080px screen sharing with large text (minimum 28pt body)
  • Chat Assets: Pre-formatted messages with links to documentation, GitHub, media kit for copy-paste during Q&A
Legal + Trademark Information
EXOCHAIN and related marks are protected trademarks of EXOCHAIN Foundation. This section clarifies trademark ownership, usage permissions, and restrictions to ensure proper legal protection of Foundation intellectual property while enabling appropriate community and partner usage.
Trademark Portfolio
Permitted Uses
No Permission Required
The following uses do not require explicit Foundation approval:
  • Accurate editorial coverage and news reporting
  • Academic research and technical publications
  • Truthful comparative advertising
  • Community discussion and commentary
  • Educational content about the protocol
  • Open-source implementations following licenses
Permission Required
Contact brand@exochain.foundation for approval before:
  • Using marks in product names or branding
  • Creating merchandise for commercial sale
  • Implying endorsement or partnership
  • Using marks in domain names or social handles
  • Modifying or creating derivative marks
  • Large-scale promotional campaigns
Prohibited Uses
The following uses are strictly prohibited and may result in legal action:
1
Confusing Similarity
Creating names, logos, or brands that could be confused with EXOCHAIN Foundation or its marks. This includes similar spellings, sound-alikes, or visual approximations.
2
False Affiliation
Suggesting your organization, product, or service is officially affiliated with, sponsored by, or endorsed by EXOCHAIN Foundation without written permission.
3
Mark Alteration
Modifying, recreating, or creating derivative versions of EXOCHAIN marks. All marks must be used exactly as provided in official asset packages.
4
Disparagement
Using EXOCHAIN marks in connection with unlawful, fraudulent, defamatory, or otherwise objectionable content that damages Foundation reputation.
Enforcement Policy
EXOCHAIN Foundation actively monitors trademark usage and enforces its rights to prevent consumer confusion and protect brand integrity. Enforcement actions may include:
  1. Informal Notice: Initial contact requesting voluntary cessation of infringing use
  1. Formal Cease and Desist: Legal notice demanding immediate discontinuation
  1. DMCA Takedown: Requests to platforms and hosting providers for infringing content removal
  1. Litigation: Legal proceedings for willful infringement or refusal to comply with notices
The Foundation prioritizes education over litigation for good-faith mistakes. Contact the brand team immediately if you receive an enforcement notice to discuss resolution options.
Crisis Communication + Issues Management
EXOCHAIN Foundation maintains consistent brand standards during crisis situations, security incidents, or reputational challenges. Crisis communications prioritize transparency, technical accuracy, and constitutional consistency while adapting message delivery to urgent circumstances.
Crisis Communication Principles
Transparent Disclosure
Provide clear, factual information about incidents without speculation or minimization. State what is known, what is unknown, and when updates will be available.
Timely Response
Acknowledge incidents within hours, provide initial statement within 24 hours, and maintain regular update cadence until resolution. Speed matters, but accuracy takes precedence.
Technical Precision
Maintain proof-first language even under pressure. Avoid hyperbolic reassurances or unsupported claims. Describe specific technical measures taken, not vague "taking this seriously" statements.
Crisis Response Framework
Security Incidents
For protocol vulnerabilities, infrastructure compromises, or cryptographic issues:
  1. Acknowledge incident existence and severity classification
  1. Describe affected systems and user impact scope
  1. Detail immediate containment actions taken
  1. Provide timeline for patches or mitigations
  1. Publish post-mortem with root cause analysis
  1. Outline prevention measures for future incidents
Reputational Issues
For misinformation, community conflicts, or governance disputes:
  1. State Foundation position clearly and factually
  1. Correct inaccuracies with supporting evidence
  1. Acknowledge legitimate concerns without defensiveness
  1. Outline governance process for addressing issues
  1. Provide timeline for community input and resolution
  1. Document decision rationale transparently
Communication Channels During Crisis
Prioritize official channels for crisis communications to prevent misinformation spread:
1
Primary Channel: Foundation Website
Publish incident notices at exochain.foundation/incidents with timestamp, severity, and detailed technical information. Treat as canonical source of truth.
2
Secondary Channel: Twitter/X
Post brief incident acknowledgment with link to full website statement. Avoid multi-tweet threads that can be quoted out of context. Pin critical updates.
3
Tertiary Channel: Email
Send direct notifications to affected parties, partners, and core community members. Include incident summary, impact scope, and action items.
4
Media Inquiries
Direct all press inquiries to press@exochain.foundation. Provide prepared statement. Do not conduct impromptu interviews without legal/leadership approval.
Brand Consistency During Crisis
Maintain visual and tonal brand standards even during urgent communications:
  • Use standard EXOCHAIN templates and formatting for all statements
  • Apply constitutional tone: calm, precise, factual—never panicked or defensive
  • Avoid all-caps, excessive exclamation marks, or emotional language
  • Include proper logo lockups and contact information on formal statements
  • Maintain technical accuracy; do not simplify to point of inaccuracy
  • Preserve proof-first philosophy: describe what is verifiable, acknowledge what is not
Brand Evolution + Versioning
EXOCHAIN Foundation brand evolves through deliberate, documented changes that maintain constitutional consistency while adapting to ecosystem growth and technical advancement. All brand modifications follow governance processes with community input and transparent decision documentation.
Version Control System
Brand assets use semantic versioning (MAJOR.MINOR.PATCH) to track changes and ensure consistency across materials:
Version Number Structure
  • MAJOR: Fundamental logo redesign, core color palette change, complete typography system overhaul
  • MINOR: New logo lockup variants, additional color additions, expanded asset library
  • PATCH: Technical corrections, file format additions, documentation clarifications
Current version: 1.0.0
Release date: 2024-01-15
Deprecation Policy
When brand elements change, previous versions follow deprecation timeline:
  • Month 0: New version published with changelog
  • Month 1-3: Transition period—both versions acceptable
  • Month 3-6: Deprecation warning for old version
  • Month 6+: Old version officially deprecated, request updates
Critical fixes (e.g., security, legal) bypass deprecation timeline.
Brand Governance Process
Proposal Submission
Community members, partners, or Foundation staff submit brand change proposals via GitHub issues with detailed rationale and mockups.
Community Discussion
Open comment period (minimum 30 days) for community feedback, alternative proposals, and impact assessment.
Design Development
Foundation design team develops refined versions incorporating community input and technical requirements.
Governance Vote
Foundation governance body votes on proposal adoption following constitutional decision-making procedures.
Implementation
Approved changes implemented with version number increment, changelog documentation, and asset package updates.
Design System Maintenance
EXOCHAIN design system receives ongoing maintenance addressing technical evolution and ecosystem needs:
90%
Consistency Target
Percentage of materials using current brand version within 6 months of release
30
Review Cycle
Days for community feedback period on proposed brand changes
4
Annual Audits
Quarterly brand consistency audits across Foundation properties and materials
Future Brand Considerations
As EXOCHAIN protocol matures, brand evolution may address:
  • Sub-Brands: Identity systems for distinct protocol components or Foundation initiatives
  • Accessibility: Enhanced color contrast modes, dyslexia-friendly typography options
  • Expanded Motifs: Additional approved visual metaphors as protocol capabilities grow
  • Localization: Market-specific adaptations while maintaining global consistency
  • Technology: Emerging format support (AR/VR, spatial computing, new web standards)
Versioning + Changelog
This media kit represents version 1.0 of the EXOCHAIN Foundation brand guidelines. All changes to brand standards, asset packages, and usage guidelines are documented through version-controlled changelog with semantic versioning conventions.
Current Version Information
1.0
Media Kit Version
Initial comprehensive release
2024
Publication Year
January 15, 2024
250+
Brand Assets
Logo variants, templates, guidelines
Version 1.0.0 — January 15, 2024
Initial Release
Comprehensive media kit establishing EXOCHAIN Foundation visual identity, brand standards, and usage guidelines for press, partners, and community stakeholders.
What's Included
Visual Identity System
  • Primary mark + wordmark + lockup variants
  • Monochrome logo adaptations (black/white)
  • Color palette specifications (HEX, RGB, CMYK)
  • Typography guidelines (Inter, JetBrains Mono)
  • Iconography + diagram style specifications
  • Imagery + photography direction
Application Guidelines
  • Usage examples + templates (press, slides, social)
  • Clear space + minimum size requirements
  • Print design specifications + paper stock
  • Website design standards + components
  • Video + motion design specifications
  • Event + conference branding guidelines
Messaging Framework
  • Brand voice + messaging guidance (proof-first, constitutional, non-hype)
  • Approved boilerplate + elevator pitch
  • Key messages (non-technical + technical)
  • Press + partner guidance
  • Trademark + legal information
Canonical Asset Locations
Official brand assets and documentation are maintained in the following locations:
Primary Repository
Version-controlled asset repository with logo files, templates, and source files. Includes release tags for each version.
Media Kit Website
Interactive web version of media kit with downloadable asset packages, usage examples, and contact information.
Design System Documentation
Technical design system documentation for developers and designers implementing EXOCHAIN brand standards.
Future Updates
Upcoming versions will be announced via Foundation channels with adequate transition periods. Subscribe to github.com/exochain/brand for notifications of brand guideline updates. All changes follow the governance process outlined in Section 28: Brand Evolution + Versioning.
Contact + Support
EXOCHAIN Foundation provides dedicated support for media inquiries, brand questions, partnership discussions, and technical assistance. Direct inquiries to appropriate channels to ensure timely, accurate responses from qualified team members.
Primary Contact Channels
Press + Media
Media relations, interview requests, statement requests, press kit questions, journalist inquiries
Response time: 24-48 hours for standard inquiries
Brand + Partnership
Logo usage approval, co-branding requests, partnership inquiries, trademark questions, asset customization
Response time: 3-5 business days for approval requests
Security Disclosures
Vulnerability reports, security research coordination, responsible disclosure, incident reporting
Response time: 24 hours for critical issues
General Inquiries
General questions, community inquiries, event information, educational requests, miscellaneous support
Response time: 5-7 business days
Additional Resources
Documentation
Community
  • Discord: Community discussion + technical support
  • Forum: Governance discussion + proposals
  • Twitter/X: @exochain — announcements + updates
  • LinkedIn: EXOCHAIN Foundation — professional network
Support Request Guidelines
To ensure efficient processing of support requests, please include the following information when contacting Foundation teams:
01
Request Context
Describe the purpose of your inquiry: press coverage, partnership proposal, brand usage, technical question, security issue, etc.
02
Relevant Details
Provide specific information: publication name, project description, intended usage, timeline requirements, affected systems, etc.
03
Supporting Materials
Attach relevant files: draft articles, mockups, technical diagrams, error logs, proof-of-concept code, etc.
04
Timeline + Urgency
Indicate deadline or urgency level: standard inquiry, time-sensitive request, critical security issue requiring immediate attention.
EXOCHAIN Foundation
Constitutional trust infrastructure for verifiable digital operations
This media kit version 1.0.0 published December 15, 2025. All content © 2025 EXOCHAIN Foundation. Trademarks and brand assets used under Foundation guidelines.