517d9a020a
koios.vector.testnet.apexfusion.org was retired and answers 503, so the "try mainnet, then testnet" resolver had nothing to fall back to. After the mainnet fix both constants pointed at the same host, which meant a transient failure on the first probe could succeed on the second and label a mainnet base as "testnet" in the UI. Mainnet or nothing. One base, one label. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UPpFgu6wXiDfJv8ghoUwBJ
AP3X Fusion — ecosystem hub
The public ecosystem site for Apex Fusion, served at https://apex-fusion.odyssey-works.io.
What this is
A single self-unpacking index.html (~2.1 MB) — React and all assets are
bundled inside it. Sections: ecosystem overview, the Vector edge, tri-chain
architecture, AP3X across ecosystems, markets, stack map, HAL 8, news,
wallets, bridges, dapps, explorers, staking, developers, exchanges.
How it is served
Caddy on the HAL 8 host serves this directory as a static site. The box
pulls this repository; there is no build step and nothing to compile —
committing to main is the deploy.
Because the site is public and carries no secrets, this repository is public too, so the host clones it without credentials.
External dependencies
Two things are fetched at runtime rather than bundled:
- three.js
0.160.0fromcdn.jsdelivr.net— powers the Fusion Chamber 3D visual (§12). If the CDN is unreachable that section degrades; the rest of the page is unaffected. - The AI assistant widget posts to
window.FUSION_AI_ENDPOINT, falling back totext.pollinations.ai. See the note below.
Note on the AI assistant
The chat widget in the bottom-right sends visitor messages to a
third-party inference endpoint by default. window.FUSION_AI_ENDPOINT
can be repointed at HAL 8's own OpenAI-compatible API
(https://hal8.odyssey-works.io/v1) so conversations stay on
Odyssey Works infrastructure.
Updating
Edit index.html, commit to main, and the host picks it up on its next
deploy tick. No build, no bundler, no CI.