Skip to main content
SDK @gol/sdk@0.9.0 is published on npm under latest and next. The hosted approval preview at https://approve.gol.network is deployed and enabled on Base Sepolia with API 0.8.0-rc.1. Real browser-wallet acceptance was skipped for this rollout; wallet/device support remains unqualified. Install the exact version with pnpm add @gol/sdk@0.9.0. The screenshots below were captured with SDK 0.8.0 and the October 13 frontend against a local Base Sepolia fork. See current availability.
GOL provides mandates for your compatible account. The owner uses their own wallet; GOL does not provide an account or hold its private key. Independent review lives on approve.gol.network, in a top-level desktop popup or a full page on mobile. The developer application cannot replace terms or signing data inside that origin. The contracts enforce limits and direct owner approval, pause and revocation remain possible without GOL. The page cannot force every developer to use hosted review.

Register a return destination

In Project settings, register an exact HTTPS callback without query or fragment. Publish the project-bound TXT challenge at _gol-approval.<domain> and verify it. A project name is display metadata. A verified domain proves control of the callback host; it does not authenticate the developer’s end user. Revocation blocks new signatures and return navigation, and does not cancel an accepted signature.
Console Project settings with an owner approval return destination and domain verification controls

Project settings registers and verifies the exact approval return destination. This console capture uses deterministic mock data.

Prepare and create on your server

Keep the test project API key on your server. Prepare the exact mandate through prepareGasPolicy, then create a session for the returned draft and registered destination. Persist the returned session ID, request ID and authority fingerprint with your application’s request before sending the launch descriptor to the browser.
Authority is immutable. Changes require a new preparation/session. Default review TTL is 15 minutes, bounded by preparation/signing expiry, with a one-hour maximum. Idempotent creation returns the same resource but delivers the capability once. If the response is lost, your authenticated server rotates the capability for that same session; the old capability stops working. Do not log the launch URL.

Open directly from a click

Obtain the descriptor before the user clicks, so browser activation can open a popup. The browser imports the browser-safe entry only and receives no project API key.
Mobile navigation destroys the original document. On the exact registered callback, call resumeOwnerApproval() once to consume the correlated result. The SDK stores only non-secret correlation, never a capability, in session storage. Popup closure returns closed; it does not reject, approve or revoke. If your application uses COOP, test its opener behavior and offer the redirect path when messaging is severed.

Review, sign and verify

Owner approval popup reviewing a bounded one USDC transfer and five USDC total allowance on Base Sepolia

The desktop popup is 540 by 780 pixels. Canonical authority supplies the readable account, recipient, spending, expiry and gas terms.

Approval terms showing expiry, delegation and ETH reimbursement limits in the desktop popup

Scroll the terms panel to review expiry, delegation and the exact ETH reimbursement limits before signing.

Owner wallet connected before consent and signing

The selected owner wallet must control this exact account. This local capture uses an injected test wallet.

Approval popup waiting for the wallet signature

The page waits for the wallet signature after the owner checks the readable terms.

Submitted owner approval awaiting chain confirmation

The transaction has been submitted and is awaiting the configured confirmation head. Inclusion remains provisional.

Confirmed owner approval with a Return to application button

A confirmed result offers the registered return path. The application still re-reads the authoritative API result.

Owner approval refusing a wallet that cannot authorize the requested account

A different wallet cannot approve the account named in the canonical request.

Full-page mobile owner approval review

Mobile review uses a full page in a wallet-enabled browser. This capture starts at 390 by 844 pixels.

The page reconstructs spending terms from canonical bytes and recomputes the commitments, exact signing payload and transaction. It checks chain, contracts, profile and current account configuration, epoch, nonce and deadlines before and after wallet prompts. It shows project/domain, account, network, agent, rules, recipients, USDC caps, effective/expiry times, no-child delegation and ETH gas terms. Unknown or inconsistent data is refused. Wallet typed prompts may contain only hashes; owner signing explains this limitation. SDK 0.9.0 and the current frontend cover the five exact account configurations in supported accounts, bounded direct USDC transfers, up to two child-mandate levels and 16 active descendants, both relayer modes and the accepted chargeable-outcome masks. The images show one Nexus 1.3.3 account under EIP-7702, with no child mandates and success-only reimbursement, as chosen by that request. An injected EIP-1193 wallet signs, broadcasts the exact transaction and pays its approval gas separately from later agent reimbursement. The five-family fork rehearsal includes Safe EOA threshold collection and the owner actions described below. It does not qualify real extensions or mobile devices. WalletConnect, contract-owner Safe signatures and app-scoped embedded wallets at another origin remain unqualified. Fresh EIP-7702 setup needs an authorization-signing adapter; ordinary injected wallets must not be assumed to provide it. The platform durably records the signed operation before returning broadcast instructions and keeps observing after the popup closes. A signed operation cannot be cancelled by clicking Decline. Inclusion is provisional; confirmed requires exact transaction/events/state at the configured Base confirmation head. Base safe is not Ethereum finality. Ambiguous sends are indeterminate, never silently retried. Treat browser messages as hints. Your server must re-read the session through getApprovalSession(projectId, sessionId), compare it with its saved request, project and fingerprint, and require confirmed before enabling the agent. A callback cannot supply replacement authority or an arbitrary return URL.

Owner control and recovery

Setup and approval are separate. An existing EIP-7702 delegation or core installation can remain even when no mandate was approved. Declining an unsigned request creates no mandate through that session. After a wallet signs, GOL cannot retract the signature; its signed deadline or nonce/epoch invalidation bounds its remaining validity. Recover accepted operations through authenticated server lookup and a fresh scoped observation capability. The launch TTL does not stop durable confirmation. Do not ask an owner to sign again just because a popup closed or a transaction hash was lost. Owners can pause/revoke directly through the contract without a page, project key or GOL API. Revocation does not undo transfers or revoke residual token allowances and other account permissions. Those require independent owner actions. Broader family and safety UI coverage requires its own exact configuration and wallet acceptance.
Owner action popup reviewing a request to pause an existing mandate

An operation-specific pause request identifies the existing mandate and its effect before asking the owner to sign.

Installation, EIP-7702 setup, pause, resume, mandate revocation, gas-policy revocation and permanent removal use separate operation-specific sessions. A setup request does not also grant a spending mandate. Safe signatures are collected from the exact EOA owners, sorted canonically, and checked again against current account configuration.