Skip to main content
Use the source-available TypeScript, Rust, and Python SDKs with your own keys and RPC connection. You need a compatible Swig deployment from your operator; Environment Setup explains how to obtain its details.

​
Build a wallet flow

Set up your environment

Choose a language and connect to a compatible Swig deployment.

Create a wallet

Deploy a wallet with a root authority and fund its vault.

Add a spending role

Give another key a native-currency allowance.

Read a role

Inspect the authority and action count before using the role.

Send a transfer

Spend from the vault; the role’s key pays transaction gas.

Send a sponsored transfer

Use a compatible bundler and paymaster to sponsor gas.

​
Choose your client

The scenario pages put each language side by side. Swig supplies contract bindings, permission codecs, and a small smart-account adapter. Sponsored operations currently use already deployed accounts and EntryPoint v0.9, with one call per operation. The shared beacon requires a compatible bundler policy. See Send a Sponsored Transfer for provider requirements and the tested SDK versions.

​
Operate a fleet

The shared beacon selects the implementation used by every wallet in the fleet. It lets an operator upgrade that fleet without individual user upgrade transactions. Bundler Compatibility covers account registration and handling operations queued during an upgrade. Building on Solana? See Swig on Solana.