About Swig
Swig is an account abstraction toolkit that empowers developers to create sophisticated, programmable smart wallets on Solana. It is open source, fast to build on, and designed to make advanced wallet functionality feel practical in production applications. Smart wallet functionality has been popular on EVM chains, but much less developed on Solana. Swig brings that layer to Solana so developers can build better onboarding, better permissions, and more programmable transaction flows without giving up user control.Current Market Problems
Developments in Web3 have brought many benefits, but simultaneously some table stakes Web2 functions have been lost along the way. Traditional crypto wallets are part of this problem:- Poor UX: Traditional wallets force users to either give up full control or do everything manually themselves. You could be the best dev, but your app’s experience would inherently be downgraded as a result.
- Payments: While crypto solves many payments challenges, the automated and configurable transaction tooling critical for most payments use cases is still limited.
- General Abstraction: Developers need to rely on users who are blockchain experts to gain traction on their apps due to limited abstraction tooling in the market.
- Onboarding: Seed phrases, onramps, and gas all make onboarding to a new app complicated. Devs are losing the battle before it even starts.
How Swig Solves These Problems
A Swig wallet is an on-chain account built inside a Solana program that can perform all standard wallet functions while adding powerful programmable features:| Swig Features | Pre-Swig Paradigm | Post-Swig Paradigm |
|---|---|---|
| 🗝️ Non-Custodial Smart Wallets Devs can create Web2 UX without sacrificing on Web3 self-custody standards | Custody vs. UX Tradeoff ❌ Devs choose between: Self-custody, but complex UX Or ❌ Custodial services, but security risks | Web2 UX + Web3 Self-Custody Control ✅ Create embedded wallets with no intermediaries ✅ Apps can request permissions without managing keys |
| ⏳ Session-Based Authorization Enable temporary, permissioned app access without constant manual approvals | Manual Approval Friction ❌ Users manually approve every transaction ❌ Apps lose traction due to “approve fatigue” | Seamless Session Mgmt ✅ Users approve once per session period ✅ Configurable time limited permissions |
| 🔓 Granular Permissions Delegate specific transaction permissions rather than full wallet control | All-or-Nothing Access ❌ Wallets require full signing authority | Fine-Grained Controls ✅ Role-based permissions ✅ Transaction-type permissions |
| 🔄 Automated Transactions Power subscription payments, payment streaming, and conditional transactions | Manual Payments ❌ Payments are not programmable ❌ Advanced payment logic done off-chain | Programmable Payments ✅ Subscription billing ✅ Payment streaming ✅ Automated rebalancing ✅ Dollar-cost averaging |
| 🌐 Social Recovery & Authentication Manage wallets using social accounts like Google, X, or Facebook through ZK proofs | Seed Phrase Vulnerability & Onboarding Frictions ❌ Complicated user onboarding ❌ No key recovery options | Familiar Recovery & Onboarding Methods ✅ Seamless Web2 user onboarding ✅ Multi-guardian recovery with trusted contacts |
| ⛓️ Chain Abstraction Operate seamlessly across multiple chains | Single Chain Limitations ❌ Separate wallets needed for different chains | Unified Multi-Chain Experience ✅ 1 wallet operates across all SVM chains ✅ Sign SVM transactions with EVM Keys |
| ⛽ Paymaster Integration Cover gas fees for users through a central account | Gas Fee Barriers ❌ Users must hold native SOL tokens for every trx ❌ High-friction onboarding ❌ App experiences can’t be “free” | No Gas, No Problem ✅ Apps cover gas for users ✅ Users can pay gas with other tokens ✅ “Freemium” app experiences possible |
Why Swig Makes Solana More Powerful
Solana combined with Swig is a game changer for developers.| Solana | Solana + Swig | |
|---|---|---|
| Payments Infrastructure | Solana is emerging as a leader in payments due in large part to its fast transaction settlement speed | Swig expands on this by allowing developers to abstract complexity and create powerful non-custodial payments solutions for consumers and businesses |
| Consumer Adoption | Solana is the hub for consumer apps | Swig dramatically improves UX for Solana app developers by enhancing key management systems to enable simple and secure product flows |
| Performance at Scale | Solana’s fast transaction speeds and low fees make it particularly attractive for high-velocity trading and payment use cases But, legacy wallet experiences limit this performance advantage with constant manual approvals and limited transaction programmability | Swig’s optimized design maintains Solana’s high speed and low fees, even with advanced wallet features |
How Swig Works
The Swig protocol operates through a role-based system that enables seamless interaction with various services and platforms on Solana. Each role has:- An authority mechanism that can include social logins, blockchain keypairs, and other authentication methods
- A set of configurable permissions that control what actions can be taken
- Optional session-based authentication for enhanced security
Architecture Principles
Swig is designed around a few core implementation goals:- High performance: Transaction flows should stay fast enough for real applications, including high-frequency and consumer-facing use cases.
- Strong account validation: Wallet operations should only run against the exact account shapes and ownership constraints the protocol expects.
- Extensible authority models: New authority types and signing systems should be addable without forcing breaking changes to the rest of the platform.
- Practical permissions: Permissions should be granular enough for real products, but still understandable to developers and auditors.
Zero-Copy and Efficient Parsing
Swig minimizes unnecessary allocation and copying where possible so transaction handling can stay efficient. That matters for both raw performance and predictable execution when the wallet is validating permissions and instruction data.Account Classification and Safety
Before processing instructions, Swig validates what each account actually is. That includes ownership checks, structure validation, and PDA derivation checks where relevant. This helps the protocol avoid acting on malformed or unexpected accounts.Extensible Authorities
Today, Swig supports multiple authority patterns already, and the architecture is designed to grow over time. That makes it possible to support richer authentication systems, broader signature schemes, and more application-specific permission models without redesigning the core wallet flow.What Comes Next
Swig continues to evolve in a few important directions:- More authority types and signing options
- Better support for AI-native transaction flows
- Stronger paymaster and sponsored transaction infrastructure
- Continued performance improvements as the protocol and SDKs mature