Separate Solana devnet preview
Solana devnet Preview 1 is enabled on the developer API with published@gol/sdk@0.9.0-solana-preview.1. Its programs, keypair-wallet USDC scope, setup flow, gas reimbursement, and finalized observation have separate guides and references. Hosted CLI acceptance checked 32 finalized receipts through two RPC operators. The app’s separate Solana devnet preview page was removed on November 1, 2026. Real wallet/device qualification, Privy devnet support, and the Squads upgrade-authority transfer remain incomplete. The preview is unaudited and devnet-only. Stable npm latest and next resolve to 0.9.0; its separate preview scope is unchanged.
Private consumer app and public access
The consumer app is in private team testing. Private Base mainnet wallet paths include swaps and owner-approved USDC spending limits (mandates); Base Sepolia and Solana devnet offer separate test-money mandate paths. Connected AI apps and GOL chat can use a spending limit only within the owner’s consent and the limit’s on-chain terms. Public mainnet access is not open. The app’s network and capability checks still apply to every feature. The personal Vault remains a preview; missing or stale catalog data prevents setup and must not be interpreted as a zero rate. This consumer scope is separate from the stable hosted developer mandate/payment release described below. Solana mainnet app features and the separate Solana devnet mandate preview are also different capabilities. Switching a wallet network moves no funds.Current Base Sepolia developer test support
GOL supports bounded USDC transfers from five reviewed account configurations on Base Sepolia testnet. The hosted service uses the October 18, 2026 version 3 core, API0.8.0-rc.1, and published @gol/sdk@0.9.0. Hosted acceptance on this deployment checks each family’s owner approval, exact transfer and retry, on-chain above-cap refusal, owner pause and resume, revocation, and signed workflow webhooks. Safe and the delegated EOA also exercise sponsored child mandates and developer-operated relaying. The acceptance record distinguishes selected Base safe confirmation from continued finalized observation. This is testnet support; wallet/device qualification remains incomplete.
Owners using the previous version 3 core must remove that installation, install the
current core and approve fresh spending limits. Account addresses and balances stay
in place; approvals do not carry across core addresses. See migration steps.
The version 2 core remains deployed, but the hosted service no longer accepts its approvals. To use the current service, an owner installs the version 3 core and signs a new approval.
The SDK section gives copy-paste guidance for published @gol/sdk@0.9.0. Its reference page can also describe an explicitly marked unreleased candidate. The hosted owner approval guide uses published SDK 0.9.0. The hosted approval preview is deployed and enabled at https://approve.gol.network on Base Sepolia. Its production UI passed the five-family local fork rehearsal, but real browser-wallet acceptance was skipped for this rollout; wallet/device support remains unqualified. Local fork screenshots do not establish real-wallet acceptance.
The public API can report provisional included after verifying an exact canonical
receipt and the expected GOL effect. The previous core’s Alchemy notification filter
has not been rebound to this deployment, so current core transactions rely on
polling reconciliation. The GOL relayer notification remains an additional trigger
for its transactions. GOL reads the transaction and receipt itself before reporting
included. A provisional result can later become orphaned, reverted, or
mismatch. Financial settlement waits for the selected Base safe head, and
background observation continues through finalized. No fixed latency is promised.
Network and contracts
Every deployment entry has a verified runtime hash and a Sourcify source match. Read these values at runtime with
getGasConfiguration instead of hard-coding them. The version 2 core at 0x77DfcE1547c687dE99FDa660d7c64bFE38b347b9 stays deployed and unchanged, but the hosted service no longer serves it.
Accounts
Safe 1.4.1, Biconomy Nexus 1.0.0, ZeroDev Kernel v0.3.1, Alchemy Modular Account v2, and an owner’s EOA delegated to Biconomy Nexus 1.3.3 under EIP-7702, in the exact configurations described in supported accounts. An account type name alone is not enough: the API checks the proxy or delegation, implementation, and installed configuration before every approval and action.Mandates and payments
Arbitrary calls, swaps, full-control mandates, and accounts outside the five configurations above are not available in the hosted service.
Limits
Service limits can pause new actions if GOL’s outstanding unreimbursed gas reaches its testnet budget. A paused action is refused before it is sent, and no value moves.