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.