Changelog
This page records changes that affect how operators, builders, and reviewers use Balchemy. It does not list private planning notes or internal roadmap details.
2026-07-03 — Controlled-live hardening and release-state alignment
Balchemy's controlled-live path was hardened across production routing, provider health, MCP exposure, public authority copy, SDK/CLI release state, and operational evidence. This update supports controlled beta review; it does not change public-launch status.
What changed:
- CX53 is the active production host, old-server cleanup is complete, and direct backend/frontend app ports remain closed from the public internet.
- Provider health and source availability now gate controlled-live arming and keep degraded or unavailable market data explicit instead of presenting empty success.
- Default public MCP exposure no longer includes
agent_execute; builders should treattools/listfor the current key and scope as the advertised capability source. - Public authority copy now separates wallet sign-in, walletless setup, runtime mode, approval, submission, and execution boundaries.
- SDK and CLI release state remains aligned on
0.3.11; this changelog entry ships no new SDK/CLI package surface. - Runtime warning hardening and Redis URL log-marker hardening reduced noisy or sensitive operational signals.
- Controlled-beta proof assets were captured for review. Public launch, fresh GitHub Actions/CodeQL/Gitleaks evidence, and offsite backup proof remain parked until separately proven.
2026-05-24 — Shadow-first control language
Public product guidance now separates the main wallet, agent trading wallet, runtime mode, funding, live arming, approval, submission, and reconciliation.
What changed:
- New operators see product proof before a wallet commitment.
- Wallet sign-in is described as signature-only identity proof.
- Submitted and reconciled outcomes are named separately.
- Unavailable or degraded evidence is shown as a limitation, not as a zero value.
2026-05-21 — Hub-only product direction
Hub is the active web product for autonomous trading-agent operations. Studio is retired as a separate bot workspace and remains only as a compatibility or retirement route.
What changed:
- New setup paths point to Hub agents instead of Studio bot creation.
- Telegram and Discord are described as Signal Sources, not chat-bot products.
- Explorer remains the public discovery and evidence surface.
- Studio-era widget, bot personality, and knowledge-training language is removed from active public navigation.
2026-05-18 — External-agent onboarding boundaries
CLI, SDK, MCP, walletless onboarding, and browser wallet sign-in are documented as different paths with different commitments.
What changed:
- Builders can start with a read-only path before adding privileged scopes.
- Walletless onboarding is documented as an MCP/CLI workflow, not a browser wallet modal step.
- Public records keep raw IDs and protocol metadata in a secondary technical layer.
2026-03-22 — Trading lifecycle hardening
Trading documentation now emphasizes policy checks, submitted state, execution state, and reconciliation state as distinct lifecycle steps.
What changed:
- Swap submission is not described as final completion.
- Fee, order, and transaction references are linked to lifecycle documentation.
- Chain-specific Solana and Base behavior remains explicit in trading docs.
2026-03-19 — Integrated documentation
Balchemy documentation moved into the main Next.js frontend so product docs, search, route state, and public navigation share one design system.
What changed:
/docs/*routes render inside the main app.- Search and mobile navigation are available from the docs shell.
- Task paths start with running an agent or integrating one, then reveal deeper reference material.