search
TelegramX Profile

screwdriver-wrenchCore Refactor: Solana-Only Runtime (03-10)

Major March 2026 internal refactor: Solana-only runtime, Solscan-first data, and hardened image-based deploys

March 10, 2026 | PLATFORM & INFRASTRUCTURE UPDATE

From March 8 to March 10, 2026, we pushed one of the biggest internal cleanups Divine has had since the Rust relaunch. Most of this work was under the hood, but it materially changed how Divine fetches market data, how Aegis evaluates Solana activity, and how production is deployed.

hashtag
What changed

  • The Graph Token API is fully gone. After repeated upstream issues, Divine is back on Solscan as the primary Solana market-data and enrichment path.

  • DIVINE is now Solana-only. We removed EVM from the runtime, config, admin controls, Telegram flows, and the remaining compatibility scaffolding still hanging around the workspace.

  • Aegis' Solana blacklist pipeline was cleaned up and hardened. Retry behavior is tighter, unnecessary requests were cut, wallet history and holder fetches are faster, and upstream noise is less likely to trigger false fatals.

  • Live Activity now uses Solana RPC for balance refreshes. Verified signal updates no longer depend on The Graph or Solscan account lookups. They now use direct RPC balance checks, including Token-2022 support and batched balance fetches.

  • CI and workspace hygiene were tightened significantly. Tests, coverage gates, dependencies, toolchain versions, docs, and internal module boundaries were all simplified.

hashtag
Infrastructure changes

The deploy model also changed materially over the last few days:

  • Divine is now built locally as a Docker image and deployed to the VPS as a single immutable runtime artifact.

  • The server no longer keeps a live source checkout. Production runs the built image plus host-managed config and state.

  • The runtime stack was hardened with health checks, a read-only filesystem, dropped Linux capabilities, tighter resource limits, and stricter systemd sandboxing.

hashtag
Why this matters

This refactor was mainly about consistency and reliability. Fewer chains, fewer compatibility layers, and fewer fragile upstream dependencies means less operational noise and a much cleaner base to build on. Divine should now be easier to maintain, easier to deploy, and more predictable at runtime.

Past announcements that mention EVM support are now historical. The current platform and documentation reflect the new Solana-only scope.

The DIVINE Team

PreviousHolder Coordination Analysis Is Now Live (03-11)NextSmol Follow-Up: Tighter Micro-Cap Filters (01-15-2026)

Last updated