Skip to main content
Use the exact package and peers from the quickstart. @gol/sdk/solana is browser-safe; it exports SolanaClient, canonical encoders, independent reads, review verifiers, instruction builders, and generated golDelegate/golMandate clients. @gol/sdk/solana/server exports createSolanaApiClient, which carries a test project API key and belongs on your application server. Webhook HMAC verification comes from @gol/sdk/server, also server-only. Keep the preview isolated from an existing Base application’s SDK dependency and wallet configuration. The regular GOL consumer app and its Privy mainnet signer are not Solana preview entry points. A Wallet Standard account must explicitly advertise solana:devnet; never fall back to a mainnet signing request.

Same-origin browser transport

The SDK requires a typed transport, not a browser API key. The project UUID may be public. This transport sends requests to your application server using your existing user session:
The server must authenticate the user and authorize the specific owner/resource and operation before using its API key. A shared project key alone does not prove that the browser user controls an owner or mandate. Use a fixed upstream origin, a fixed project, an explicit route allowlist, CSRF/origin protection, request limits, and no-store responses. Do not build a general URL-forwarding proxy.

Server proxy pattern

This handler factory can be mounted as your server’s POST handler. Supply authorize from your application’s session and owner/resource authorization layer. It must fail closed and must not accept a browser-supplied owner assertion as proof. It is intentionally a required dependency, not an always-true sample authentication check.
Issue the server key for the minimum scopes your proxy needs. Webhook creation/secret management should stay in a separate server administrative flow, so it is absent from this browser allowlist. Add application rate limits and bounded transport error handling; do not expose upstream exception objects or private provider URLs. Retain an operation’s draft ID/action ID across retries. Canonical request validation and authority enforcement remain in the platform and on-chain programs. The SDK reference lists the exact entry-point declarations; the API reference lists the route schemas and scopes.