Composable surfaces, cleaner routing boundaries.

Vestige separates the premium static layer from the execution runtime so research, documentation, and product narrative stay fast, indexable, and stable. Route engines, wallet connectors, and heavier liquidity modules are loaded only where execution actually happens.

Static shell

Research, documentation, public trust, and protocol narrative stay fast, indexable, and stable in the Next.js App Router layer.

Lazy runtime modules

Swap, trade, markets, and live VIGIX logic load only when users enter those routes, keeping wallet and route initialization off the public shell.

Shared identity

The same Vestige navbar, original logo, route links, and footer now bind together the static and functional surfaces into one product system.

UTXO Suite

Security analysis, route intelligence, SDK, CDN, and API surfaces can evolve as a separate product layer without loading wallet runtimes on static pages.

Current split

Static pages use the shared Next shell for homepage, protocol pages, VIGIX information, security posture, and public policy content.

Functional routes preserve the current swap, trade, markets, and VIGIX logic while inheriting the same cross-page navigation and brand format.

UTXO Suite stays static for product education, then exposes SDK, CDN, and API entry points when real integration keys and release builds are ready.