Swig

Swig is an account abstraction framework and developer SDK for building programmable smart wallets on Solana. Built by Anagram, Swig transforms standard Solana accounts into flexible, policy-driven wallets that can be controlled by multiple authority types, delegated to other parties with fine-grained permissions, automated with session keys, and recovered without seed phrases. The project positions itself as foundational infrastructure for the next generation of Solana applications, particularly those targeting consumer onboarding, team coordination, and autonomous agent workflows.

What Swig Is

At its core, a Swig wallet is a Solana on-chain program that replaces the conventional keypair model with a richer account architecture. Instead of a single private key controlling all assets, a Swig wallet stores structured data about authorities—who can sign—and permissions—what each authority is allowed to do. That combination lets developers build wallet experiences that behave more like programmable accounts than static key stores. The project uses the tagline "Wallets, But Smarter," reflecting its goal of bringing programmability and usability to a part of the Solana stack that has historically required third-party custody or complex multisig arrangements to address.

How It Works

A Swig wallet is created as a Program Derived Address (PDA) on Solana. Creating one costs less than $0.30 in rent. The wallet stores a set of roles, each combining an authority with a bounded set of permissions. Swig supports up to 65,000 distinct roles per wallet.

Authorities in Swig are not limited to native Solana keypairs. The protocol accepts Google OAuth credentials, one-time-password authentication, Ethereum keypairs, and Secp256r1 (P-256) keys such as those used by hardware passkeys. This means users can authenticate with familiar web2 credentials while controlling on-chain assets directly, without handing keys to an intermediary.

Permissions specify what an authority can do: transfer SOL or SPL tokens, stake, interact with specific programs, spend up to a defined limit, operate within a time window, or initiate pull payments and subscriptions. Permissions can be granted or revoked at any time by a root authority.

Session keys are a key application of this model. Instead of asking a user to sign every transaction, an application can request a time-limited session key with constrained permissions. The user approves once; the app transacts freely within those bounds. This reduces approval friction for high-frequency interactions such as gaming, trading, or streaming payments.

Integration Layers

Swig is designed in five discrete layers to accommodate different developer needs:

• Protocol — The on-chain Rust program, open-sourced under AGPLv3 and deployed on Solana.
• Protocol SDK — TypeScript and Rust libraries for direct protocol interaction.
• Developer SDK — A hosted abstraction layer handling transaction preparation and wallet operations.
• Developer API — REST endpoints for backend services that need to interact with Swig wallets.
• IDP SDK — An identity provider layer wrapping OAuth and OTP flows, creating Swig sessions from standard login events.

Developers can engage at any layer, from raw protocol calls to fully hosted workflows where Swig manages all wallet infrastructure. A developer portal launched in January 2026 provides a dashboard for creating and managing projects, configuring paymasters, defining spending policies, managing API keys, and viewing transaction history and analytics.

Paymaster and Gasless Transactions

Swig includes a paymaster service that allows developers to sponsor transaction fees on behalf of users. A new user can sign up with an email address, have a Swig wallet created for them, and execute their first transactions without ever holding SOL. This removes a core onboarding barrier for consumer applications where acquiring gas tokens before doing anything else drives significant user drop-off.

Paymasters are configurable with policies limiting which transactions can be sponsored, preventing abuse while maintaining broad gasless coverage for intended user actions.

Account Recovery

Account recovery in Swig uses a guardian model. Users can designate one or more guardians—other keys or social accounts—that can authorize a recovery flow if access is lost. Recovery is implemented at the protocol level rather than through a centralized custodian, preserving non-custodial properties while addressing the practical problem of key loss. The documentation covers adding guardians after wallet creation and executing recovery flows when needed.

Ecosystem Integrations and Use Cases

Glider, an Anagram-built product for automated multichain portfolio rebalancing, was the first production user of Swig. The Swig-Para integration, announced in mid-2025, pairs Swig's smart wallet infrastructure with Para's embedded wallet and social login system, enabling developers to combine email or social onboarding with programmable wallet features in under 30 minutes. Additional integrations include Anchorage Digital for institutional custody, as well as Avichi and X42/Corvettz for identity-aware finance applications.

The documentation includes worked examples covering Jupiter DEX swaps via Swig, recurring subscription payments, sub-accounts, multi-authority configuration, and migration from Squads multisig. A Swig MCP server is available for integrating wallet management into AI agent workflows.

Security and Audit

The Swig on-chain protocol was independently audited by Accretion in 2025 (report reference A25ANA2). The audit PDF is published in the swig-wallet GitHub repository under /audits/. Anagram has stated plans for additional audits covering the developer SDK and IDP SDK as the product matures. The protocol is fully open source under AGPLv3, enabling independent inspection of all on-chain logic.

Version v1.3.1 of the core protocol was released in October 2025, with the TypeScript SDK reaching its v1.0 stable milestone alongside it.

Token

Swig has no native token. The protocol is developer infrastructure; there is no associated governance or utility token.

Team

Swig is built by Anagram, a Solana-focused development studio. Justin Blumenthal serves as CEO and presented Swig at Solana Breakpoint 2025 in a product keynote. Anagram also develops Glider, the portfolio automation product that serves as Swig's most prominent production deployment. The project's GitHub repository is maintained under the anagrambuild organization.

Ecosystem Position

Swig addresses a long-standing gap in the Solana developer toolkit. Account abstraction has been a significant unlock on Ethereum—enabling smart contract wallets with social login, gas sponsorship, and programmable permissions—but Solana's distinct account model required a purpose-built solution rather than a port of EVM primitives. Swig's approach uses a native Rust program, SVM-compatible architecture, and a multi-authority design that targets Solana's specific performance characteristics. Solana's official account featured Swig in May 2025, reflecting recognition from within the broader Solana Foundation ecosystem.