Abstract
This proposal defines the theming engine behind OpenScan.AI’s Explorer-as-a-Service offering: a configuration-driven system that lets partner chains deploy a fully branded explorer instance — logo, colors, typography, navigation, and chain identity — without forking the codebase.
Motivation
Every chain needs a quality explorer, but few teams want to build or maintain one. White-label deployments are a core milestone of Phase 4 (Enterprise) of the 2026 roadmap. A robust theming engine is what makes those deployments cheap to operate: one codebase, many branded instances.
Specification
- A single declarative theme configuration (JSON/YAML) per deployment covers: brand name, logo assets, color tokens, typography, navigation links, footer content, and social metadata.
- Theme values compile to design tokens consumed by the explorer UI at build or boot time; no per-instance code changes.
- Instances run on managed infrastructure with per-instance domains and TLS.
- A theme preview mode lets partners iterate on branding before launch.
Open questions
- Should partners be able to inject custom pages (e.g. ecosystem landing pages), or is theming limited to the explorer surface?
- Dark/light default behavior per instance vs. user preference.
Milestones
- Token-based theming across all explorer pages.
- Self-serve theme configuration and preview.
- First partner deployment on a non-XDC chain.