- The Spending limits page adds Solana devnet beside Base mainnet and Base Sepolia, and selects it by default for Solana owners. The owner chooses the agent connection, recipient, limits and expiry. The app verifies and simulates both setup transactions on devnet, then asks the wallet once. Pause, resume and revoke follow the same review.
- GOL chat and connected AI apps can read a Solana devnet spending limit, send test USDC within it and follow the transfer. The connection must be signed in with the owner’s Solana wallet and include Solana devnet in its consent. Base recipients are refused on this network. A transfer inside the limit needs no new owner signature; changes to the limit stay owner-confirmed.
- Owner requests on
/signand inside chat accept Solana devnet. Turning on chat spending for a Solana owner signs with the Solana wallet. - The app’s separate access-coded Solana devnet preview page was removed. Solana devnet Preview 1 on the developer API and its
solana-previewSDK package are unchanged. - Release checks covered service health and the public tool catalog. No Solana wallet setup or agent transfer was completed for the release, and wallet/device qualification is incomplete. This is unaudited devnet support with test USDC, not Solana mainnet support.
- In Claude, Codex or another connected AI app,
gol_connectreports the connection, the accounts it shares and the permissions it keeps. When you are signed out, it opens GOL sign-in. gol_disconnectends that AI app’s own connection, and Connections then shows it as disconnected. Wallet signers and on-chain spending limits are unchanged. GOL chat’s own connection is not ended this way.- The Spending limits page can turn on spending for GOL chat with one wallet signature over the displayed opt-in text, and turn it off without a signature. GOL chat then appears in the connection picker like any other AI app. Disconnecting GOL chat in Connections stops its payments; its spending limits stay on chain until you pause or revoke them.
- Chat reports a spending limit payment as paid only after its Base or Base Sepolia transaction is finalized, and opens agents it creates or changes inside the conversation.
- A Solana wallet can approve an AI app’s connection request. Connections without a Base wallet no longer list the Base spending limit tools, and calling one explains that a Base wallet is required. More Base and Solana wallets can sign in, and the app shows a wallet’s refusal.
- Release checks covered service health and the public tool catalog. Connecting and disconnecting from Claude or Codex, and connecting with a Solana wallet, were left for owner testing.
- Wallet-confirmed features can be started three ways: manually in the app, from GOL chat, or from an external agent such as Claude or Codex connected to
https://mcp.gol.network/mcp. Requests from chat and AI apps open atapp.gol.network/sign, where you review them and sign in your own wallet. - This covers spending limit setup and changes, native SOL staking, Jupiter Lend, token launches and creator fee claims, live trading grants, and Vault creation and top-up. Solana owners and wallet-only owners can sign in on
/sign. Vault creation and top-up use a USDC transfer authorization instead of a separate token approval. - Each AI app connection is bound to one wallet. To request Solana actions from an AI app, connect it with your Solana wallet.
- No wallet transaction was signed for the release. Vault creation and top-up requests were refused during release checks while Vault funding qualification continues. Live trading grants still require the app’s embedded execution wallet.
- Spending limits supports owner-approved native USDC limits on Base mainnet, beside Base Sepolia test money. Base mainnet uses a newly deployed GOL mandate core. Existing Base Sepolia limits are unchanged, and approvals do not carry between networks.
- These direct wallet spending limits are separate from the hosted developer gas integration, whose account support remains on Base Sepolia. See current availability.
- Funding and automatic rebalancing for the personal Base Vault were switched on for private testing. Vault remains a preview: funded deposit, withdrawal and rebalance settlement are not qualified, and the app’s availability messages show whether funding is open.
- The Explore x402 tab adds a payment network picker with Solana mainnet and Whitechain Sepolia beside Base mainnet.
- Real wallet signing and live transfers were not exercised for the release. The contracts are unaudited.
- The new Spending limits page, on Base Sepolia at launch, lets an owner approve a USDC spending cap in their wallet and create a limit for a connected AI app with one allowed recipient, a per-transfer amount, a total and an expiry of 1 to 30 days. The owner pauses, resumes or revokes each limit from their wallet.
- Connected AI apps can read their spending limits, send within them and follow each transfer through
gol_allowance_permissions,gol_allowance_transferandgol_allowance_status, after the owner grants explicit spending consent. - Owner confirmation moved to
/sign, with/sendkept as an alias. Owner-confirmed wallet transfers support Base mainnet, Base Sepolia and Solana mainnet. - Explore adds an x402 tab for discovering paid API providers on Base mainnet, with search, categories and provider details. At activation the catalog listed 2,702 providers and 92,581 endpoints; it refreshes about every 30 minutes. This release covers discovery only, not paying for x402 endpoints. See x402 services.
- Owner wallet signing, spending limit creation and authenticated AI app transfers were not exercised during the rollout.
- The hosted GOL MCP server at
https://mcp.gol.network/mcpconnects AI apps such as Claude and Codex to your GOL account. The AI app opens GOL sign-in and a consent page where you choose the account and the permissions to share. Its tools read wallet balances, activity, agents and accounts, and prepare actions for your review. - The app signs in with a connected wallet: Solana wallets through Wallet Standard and Base wallets through EIP-6963 sign a GOL challenge. Signing in proves control of the wallet only; it creates no wallet and grants no spending authority. The embedded wallet remains for the Vault and legacy owner pages.
- A production check with a disposable Base mainnet wallet completed sign-in, read-only consent, tool listing, token refresh and revocation. Other AI app clients and devices are not qualified.
app.gol.networknow asks for a team access password before any page. Without it, pages redirect to the access screen and app APIs answer401. The password is separate from wallet sign-in and grants no account or wallet authority.
- Chat embeds the app’s manual product controls, so supported actions such as swaps and native staking are reviewed and signed inside the conversation with the same checks as the app.
- Explore adds Stake for delegating native SOL to the Jupiter validator, with stake accounts, unstaking and withdrawal. Lend adds Earn and Borrow detail pages.
- Connected-owner transaction settlement was not verified at release.
- Live trading services on Solana and Base were enabled for teammate testing. New strategies still start in paper mode. Each owner approves GOL’s session signer and signs a bounded wallet trading grant before an agent can trade real assets.
- Relay cross-chain deposits can move USDC from six supported EVM chains to Solana; the owner signs each bridge step in their wallet.
- Explore adds Jupiter Lend Earn and Borrow and a News workspace. Liquid staking tokens can be found in Explore and managed from Home through swaps.
- Launchpad creates Jupiter Studio token launches and claims creator fees, signed by the owner’s Solana wallet.
- Real owner approval, launch submission, bridge completion and trade settlement were not verified at release.
- The new App tab is a guide for app users, separate from the developer guides. Its screenshots come from the app in mock mode and move no funds.
- The Solana devnet Preview 1 pages moved to Code examples. Earlier
/solana/*links redirect.
- Published
@gol/sdk@0.9.0selects the reviewed Nexus 1.3.3 delegated runtime by chain. Stablelatestandnextresolve to 0.9.0; the separate Solana devnet preview remains unchanged. - The developer API, gas worker and hosted approval frontend use the new Base Sepolia version 3 core and exact registry SDK. All five reviewed account families passed live owner approval, transfers, retries, above-cap refusal, pause, resume and revocation. Safe and the delegated EOA also passed sponsored children and developer-operated relaying. Signed webhooks covered every collected execution and verified retry delivery.
- Owners moving from the previous core must remove it, install the current core and approve fresh limits. The consumer app guides the two owner transactions; see migration steps.
- Current core inclusion uses polling reconciliation; the existing GOL relayer hook is an additional trigger. Hosted receipt reads use one RPC operator. Selected
safeconfirmation and continuedfinalizedobservation remain distinct. Real wallet/device qualification is incomplete, and this release is unaudited testnet availability.
- Explore shows Solana token markets with price charts and a curated directory of 18 Solana sites, readable without wallet sign-in. Prices refresh through 15-second polling, tokenized stocks and ETFs have their own category, and unavailable history shows a dash instead of an invented value.
- Base and Solana wallets appear in one wallet view. From October 19, token pages also open a swap beside the chart.
- Explore does not enable trading by itself; a swap still needs the selected network’s execution service and your wallet signature.
- The separate Solana devnet section covers the deployed authority and mandate programs, quickstart, browser/server integration, lifecycle, owner safety, and explicit webhooks.
- Published
@gol/sdk@0.9.0-solana-preview.1is available undersolana-preview, with exact Kit/codecs peers8.4.0. Stablelatestandnextremain0.8.0. - The developer API and private hosted app preview are enabled. Hosted acceptance checked 32 finalized receipts through two independent RPC operators, including exact-byte restart recovery and HMAC/retry/deduplication.
- Real-wallet/device qualification, Privy devnet support, and the Squads upgrade-authority transfer remain incomplete. This is unaudited devnet preview availability, not stable or mainnet support.
- Published
@gol/sdk@0.8.0adds canonical approval verification, correlated popup/mobile results, server-side sessions and operation-specific owner actions while preserving the consolidated public entry points. The registry archive matched the verified main archive byte for byte. latestandnextresolve to 0.8.0 after hosted API activation. Pin 0.8.0 and its exactviem@2.54.6dependency.- API
0.8.0-rc.1and the isolated approval frontend are deployed and enabled atapprove.gol.networkon Base Sepolia. Real browser-wallet acceptance was skipped for this rollout; wallet/device support remains unqualified. - The hosted owner approval guide shows the real production frontend against a local Base Sepolia fork at block 47663807. SDK publication and local screenshots do not establish deployed-origin or real-wallet acceptance. Check availability for current hosting status.
Type provisional inclusion in the SDK
- Published
@gol/sdk@0.7.1types the four opt-in*.inclusion_updatedevent names and payloads, socreateWebhookEndpointcan subscribe directly.isInclusionWebhookEventnarrows a verified delivery to one inclusion payload type. Endpoints without explicit opt-in continue to receive their prior selected-head events. waitForGasPolicySafetyActionInclusionandwaitForGasPolicyRevocationInclusionreport checked provisional observations for owner pause, resume, and revoke or gas-policy revocation. They use a one-second default interval and a 120-second timeout. Continue to selected-head confirmation for the final outcome.- SDK 0.7.0 was deprecated because its npm archive contained stale compiled files and omitted these interfaces. Install 0.7.1 for the corrected package.
- This SDK publication does not change the deployed API, version 3 contracts, supported account configurations, or the earlier five-family hosted acceptance record.
Subscribe to inclusion changes
- API 0.7.0 adds four opt-in signed outbound event types for provisional action or claim, owner policy, child mandate, and EIP-7702 setup inclusion. Each event identifies the transaction and resource, its observed state, and a sequence. A later
orphanedormismatchcan retractincluded; none of these events confirms or settles a transaction. - Console 0.3.0 shows provisional inclusion and its history in Gas activity. Its Webhooks form offers the four opt-in event types separately from selected-head events.
- Existing endpoints continue to receive their prior selected-head event set. To opt in, create an endpoint with explicit
*.inclusion_updatednames. At the API deployment, SDK 0.6.1’s endpoint input type predated these names, so console 0.3.0 or the public API was needed to create an opted-in endpoint. Its webhook verifier could still verify a signed delivery. - The API deployment does not change the version 3 core, Active Base Sepolia account configurations, or the September 28 five-family hosted acceptance record. The earlier continuous inbound Alchemy hooks still wake GOL’s exact receipt check; they are separate from these outbound developer events.
Projects belong to workspaces
- API 0.6.1 and console 0.2.0 add a personal workspace after verified sign-in, an optional setup checklist, a workspace selector, Team with four fixed roles and project scopes, invitations, and offboarding key review. Existing project IDs and their resources remain stable. The console remains behind its access gate.
- Published
@gol/sdk@0.6.1adds typed workspace, member, invitation, and onboarding methods toGolManagementClient. Workspace routes require a developer session; project API keys cannot manage team access. Console Owner is not wallet owner or mandate authority. - API 0.6.1 was superseded later the same day by API 0.7.0. This release did not change the version 3 core or repeat the five-family hosted gas acceptance. The promotion verified the deployed identities, migration, gate, and unauthorized route rejection; it did not complete a production developer sign-in or send a real invitation.
Faster included without new client code
- Signed Alchemy Custom Webhooks now run continuously on Base Sepolia for transactions sent to the mandate core or by the GOL relayer. In fresh hosted tests on an EIP-7702 delegated EOA, GOL verified
includedabout two seconds after the block for a sponsored setup, owner approvals and revocations, a sponsored child mandate, and developer-relayed and GOL-relayed USDC actions. - A notification only wakes GOL’s own exact receipt, canonical block, and expected-effect check; it never authorizes a mandate or records a charge. Owner confirmation and financial settlement still wait for the selected Base
safehead. The notification and receipt reads come from one Alchemy operator. - When a notification is missing or the hooks are paused, reconciliation still reports
included. In the paused-hook test it did so about 11 seconds after GOL recorded the transaction. No latency is guaranteed on this testnet service. - No API or SDK change is required.
@gol/sdk@0.6.0inclusion wait helpers already check every second.
Prompt transaction feedback on Base Sepolia
- API 0.6.0 exposes a distinct provisional
includedobservation after checking the exact canonical receipt and expected GOL effect. It can also reportreverted,orphaned, ormismatch. Owner confirmation, financial settlement, and gas accounting still wait for the selected Basesafehead; background observation continues throughfinalized. - Signed Alchemy Custom Webhooks triggered hosted inclusion for a sponsored EIP-7702 setup, owner approval, and developer-relayed USDC action. A reverted core transaction, signed replay, wrong-network request, and a fresh no-hook reconciliation path were also checked. This was a bounded test of the two hook filters. Continuous webhook delivery and fixed latency are not promised. The webhook and HTTP receipt checks use one Alchemy RPC operator, rather than independent providers.
- Published
@gol/sdk@0.6.0adds typed inclusion fields and one-second inclusion wait helpers. The existing final-confirmation helpers retain their 15-second default checks. - The five-account-family hosted acceptance remains the September 28 record run with API and SDK 0.5.0. This inclusion release did not repeat that matrix or change the version 3 core.
Developer project foundation
- Create and switch between multiple test projects in the hosted console. Each project keeps its own API keys, webhooks, gas activity, and audit history. Project pages have stable URLs.
- Copy the Project ID from Overview or Project settings. Change a project’s display name without changing its ID or slug.
- Read older audit events with cursor pagination. Gas activity and audit controls that have data now navigate and filter; unfinished controls are disabled and marked Coming soon.
- API 0.5.1 and
@gol/sdk@0.5.1add the owner-scoped project update and audit pagination interfaces. The version 3 core, hosted gas public API revision 2.0, and Base Sepolia account support do not change. The hosted gas acceptance matrix was last run with API 0.5.0 and SDK 0.5.0.
Privy and AgentKit application example
- The DeFi agent example shows a Privy embedded EOA owner, a bounded GOL mandate, and an OpenAI agent using Coinbase AgentKit to request USDC transfers through the public SDK and API.
- Local owner setup, approval, and one agent transfer have Base Sepolia receipt evidence. The demo’s hosted authenticated journey, owner-specific on-chain refusal, and delegation reset remain unverified.
- This documentation publication did not change API 0.5.0,
@gol/sdk@0.5.0, or Active Base Sepolia account support.
Unpublished console access
- The hosted developer console now requires an internal access password before its existing developer email sign-in. An unauthenticated visit redirects to
/gate; unauthenticated API requests receive 401. - This console promotion did not change the hosted API, published SDK, or Base Sepolia account and mandate support. Existing project API keys still authenticate directly to the public API.
- The console walkthrough screenshots show screens after access and were captured from the previous deployed console source, before the gate.
Consistent console branding and current integration screenshots
- Sign-in, project setup, loading, and the console sidebar use the same scalable GOL wordmark as the website and documentation header.
- The quickstart and integration guides have refreshed console screenshots, generated with mock data from the deployed console source.
- The integration documentation continues to target the supported Base Sepolia setup, API 0.5.0, and
@gol/sdk@0.5.0. Network gas reimbursement, developer relayers, and mandate trees retain their existing release scope.
Inline gas, EIP-7702 accounts, developer relayers, and mandate trees
- The hosted service moved to the version 3 mandate core on Base Sepolia for bounded USDC transfers from 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 Nexus 1.3.3 under EIP-7702. Owners with approvals for the version 2 core install version 3 and approve again.
- Network gas is reimbursed inline. The approved relayer sends each action and the contract pays it back from the owner’s account in the same transaction, within the owner’s caps and the maximum charge the agent signed. A reverted transaction can still be claimed later with the owner’s consent and GOL’s relayer.
- A developer-operated relayer can send actions and be reimbursed inline when the owner approves its submitter and recipient.
- An owner’s existing EOA can join through EIP-7702 as the fifth account family, delegated to Biconomy Nexus 1.3.3. GOL can sponsor the one-time setup.
- An agent can delegate narrower child mandates to depth 2, billed to the root’s gas policy, and the owner can pause, resume, or revoke any mandate in the tree.
- API 0.5.0 serves hosted gas public API revision 2.0, with the
not_chargedand developer relayer execution states and child mandate and EIP-7702 setup webhooks.@gol/sdk@0.5.0covers every new route and payload; it changes owner signing for the version 3 core. - The console’s Gas activity page shows relayer modes, mandate trees, and inline settlements.
SDK documentation section
- A dedicated SDK section now covers installing the package, the browser-safe
@gol/sdkentry point, the server-only@gol/sdk/serverentry point, owner signing, the API clients, execution and observation, webhooks, and errors. - The SDK reference is generated from the published package’s own type declarations by
pnpm sdk:reference, and every example is compiled against@gol/sdkinstalled from npm bypnpm sdk:examples. Fix the generator or the SDK source instead of editing the generated page. - Integrate hosted gas remains the single end-to-end walkthrough and is cross-linked rather than duplicated.
@gol/sdk@0.3.0. The hosted service moved to version 3 on September 28. See current availability.Audit log and console usability
- The audit log is a filterable, paginated table of actor, action, resource, correlation ID, environment, and time. Select an event to see its event and correlation IDs, metadata, and raw JSON.
- Revoking an API key and deleting a webhook endpoint now ask for confirmation in the console.
- Console text is larger, and pages, panels, and dialogs animate. The console follows your system’s reduced-motion setting.
- The console no longer offers linking a Google account after email sign-in. Use Google sign-in when Google verifies your email address; otherwise sign in with the email code.
Developer sessions and SDK 0.4.0
- API 0.4.0 was deployed with developer session renewal and revocation routes. The API reference now includes these routes.
@gol/sdk@0.4.0was published withGolManagementClientmethods for Google sessions, renewal, and revocation. It initially carried the npmlatestandnexttags, which moved to 0.5.0 on September 28.- Google sign-in remains disabled on the hosted console until its provider setup and a real sign-in round trip are verified. The SDK method and API route do not establish that the hosted sign-in flow is available.
Owner pause and resume on Base Sepolia
- The Base Sepolia hosted service supported bounded USDC transfers from Safe 1.4.1, Biconomy Nexus 1.0.0, ZeroDev Kernel v0.3.1, and Alchemy Modular Account v2 through the version 2 mandate core, with postpaid ETH gas reimbursement.
- API 0.3.0 and
@gol/sdk@0.3.0added owner pause and resume for a mandate bound to a gas policy. - Hosted confirmation and settlement use the lower Base
safehead, with observation continuing throughfinalized. A result atsafeis not an Ethereum finality claim.
Hosted gas payout and receipt verification
- The hosted service continued to support bounded USDC transfers through the version 2 core from Safe 1.4.1, Biconomy Nexus 1.0.0, ZeroDev Kernel v0.3.1, and Alchemy Modular Account v2, with API 0.2.0 and
@gol/sdk@0.2.0. - Owner-approved gas reimbursements began paying the GOL relayer directly. Owners whose earlier approvals named a different recipient had to approve again.
- Receipt verification used Alchemy and Base as independent providers, waiting for the lower
finalizedhead at this stage.
safe head, as described above. See current availability for support today.First hosted-gas SDK package
@gol/sdk@0.2.0was published with browser-safe owner signing and account-operation helpers at the root entry point.- Server-side API clients and signed webhook verification were published at
@gol/sdk/server. - Hosted Base Sepolia acceptance used this package for bounded USDC transfers from Safe, Nexus, Kernel, and Alchemy accounts through the version 2 core, with postpaid ETH gas reimbursement.