Swig is an account abstraction toolkit that enables developers to create powerful, programmable Solana smart wallets. With Swig, developers can integrate advanced wallet functionalities like delegating access controls, fine-grained permissions, multi SVM support, social sign-in and recovery, pull payments, and even using non-Solana identities like your ETH keypair or Bitcoinkeys to sign Solana transactions. (1)
As crypto ecosystems continue to evolve, creating a seamless multi-chain user experience is essential. We at Anagram believe Swig is the missing protocol to unify all of your on-chain activity into a single wallet with multichain composability; all while maintaining a user-friendly interface and self-custodial key management. Whether you’re building DeFi apps, NFT marketplaces, or next-gen consumer wallets, Swig unlocks new possibilities for wallet design and interoperability.
The Limits of Smart Wallets Today
Smart wallets have become increasingly popular in recent years because of the functionalities they extend to a traditional wallet. A smart wallet is a non-custodial crypto wallet powered by a smart contract, and by leveraging smart wallets, you can enable functionality including automated transactions, multi-signature support, and delegated spending limits. Smart wallets have also been widely adopted by developers with deployments on multiple chains due to their chain abstraction functionality, which can greatly simplify the user experience.
While smart wallets have largely penetrated Ethereum, we believe that Solana represents a massively underserved community that can benefit from smart wallets for three distinct reasons:
- Payments: Solana has emerged as a leader in the payments category. Smart wallets allow developers to abstract the complexity of blockchains and facilitate powerful non-custodial payments solutions to consumers and businesses. We envision Swig powering the next generation of payment applications.
- Consumer Adoption: Smart wallets provide considerable improvements in user experience, and Solana is a hub for consumer applications. Swig can be the lynchpin that allows existing key management systems to build simple and secure product flows for any segment of user.
- Low Friction UX: Solana’s fast transaction speeds and low fees make it particularly attractive for high-velocity trading and payment use cases. Swig allows developers to match Solana’s speed and avoid fragmenting the performance of an application with the inconvenience of legacy wallet experiences.
Smart wallets today are disconnected from reality, leaving SVM developers to deal with:
- General lack of Solana smart wallets: Smart wallets have supported Ethereum and other EVMs for years but only recently have limited support extended to Solana developers.
- Interoperability Challenges: Wallets on Solana and Ethereum operate in silos, making it difficult for users to interact seamlessly across both ecosystems or even when using different apps on the same ecosystem.
Swig, a cross-SVM smart wallet built by Solana developers for Solana developers, is being introduced to unlock a range of new use cases and empower the next wave of Solana Dapps.
Introducing Swig
The Anagram Build team is building Swig - a smart wallet framework that is designed to simplify wallet interactions, improve user experience, and make account abstraction accessible to developers.
Key Features
- Non-Custodial Smart Wallets: Embedded wallets with no intermediaries. Developers can request permissions on a user’s Swig, but never have to manage their keys or trust a third party. Permissions you can delegate to other wallets include withdrawal limits, staking vs transfer restrictions, and time-based limits.
- The End of the Multi-Wallet War: One Swig is all you need, no more wallets for each and every app.
- Granular Permissions: Users can delegate transaction-specific permissions rather than handing over full control.
- Identity Attestation: Prove wallet ownership by using a proxy wallet to connect to applications to avoid potential honeypots.
- Session Keys: Enable temporary, permissioned access for applications and smart contracts to take actions on your behalf without needing constant manual approvals.
- Automated Transactions: Power pull payments including, but not limited to, subscription-based payments, payment streaming, and conditional transactions.
- Paymaster: As a developer you can have a single central account that can be used to pay for gas for any of your users’ wallets, removing the need for users to deposit gas in order to make their first transaction.
- Social Management: Using zero knowledge proofs, a user can manage their Swig just by using their X, Facebook, and Google.
- Chain Abstraction: A Swig can exist on multiple SVM chains making the experience seamless across the Solana-verse.
Swig Use Cases
The first customer of Swig will be Glider (2), which leverages account abstraction to automate multichain trading strategies. Glider seamlessly rebalances your portfolio across any EVM chain without the user needing to sign manual transactions each time they wish to perform an action, in a completely non-custodial way so that users are in control of their keys the whole time. Glider has previously been limited to only creating strategies on EVM chains due to the lack of practical Solana smart wallet support. Existing solutions are too expensive, or rely on trusted intermediaries.
Swig can enhance a number of existing user experiences, such as:
- Wallets that support both Ethereum and Solana can benefit from a unified signing experience;
- Onramps wanting to support user deposits from both Solana and Ethereum into a single application;
- AI Trading Bots who might work in groups and want shared access to a single crypto wallet, but each with different levels of authorization; and
- Unified User Experience Across SVM Chains, as network extensions or L2s increasingly support Solana developers, they can use Swig to abstract away the experience of having to bridge cross-chain and switch networks, instead you can control your funds on any SVM chain using your favorite Solana wallet on Mainnet
… as well as unlock new use cases such as:
- Subscriptions: Finally, you can subscribe to that cat meme AI generator for 10 USDC a month.
- Programmable DeFi Wallets: Automate investments, recurring payments, and lending activities without relying on centralized custodians.
- Enterprise Wallets: Companies can delegate access to employees with pre-defined permissions, improving security and efficiency.
- Cross-Chain Gaming and NFTs: Enable seamless asset management across multiple chains for blockchain-based games and NFT platforms.
How Does Swig Work?
The Swig protocol is a wallet built inside a Solana program. A Swig is a Solana account that lives on-chain and has data in it that represents the authority structure of the wallet. A Swig wallet can do anything that a standard Solana keypair wallet can do: transferring assets, depositing into DeFi protocols, delegating to validators and speculating on your favorite memes. Swig is built on a role-based system that allows a user to interact with a wide variety of services, apps or platforms on Solana seamlessly and securely.
A role has an authority mechanism and a set of permissions. The authorities are flexible to allow a user or an app platform to design the perfect wallet solution. An authority can be a Google login session, X account ownership, a Solana or Ethereum keypair, and much more. These authorities open up new ways to interact with a Solana wallet and make new user experience flows possible. The permissions assigned to the role determine what can happen: think of these like mobile app permissions, but with flexible controls over specific assets, staking accounts and even other Solana program interactions. Along with permanent authorities, Swig can enable session-based systems where the authority needs to re-authenticate in order to continue operating. This is an industry standard in Web2, but in crypto, if you lose your keys, you are done. Swig sessions allow even greater security by eliminating key reuse, and ensuring that apps connected to your Swig can't establish control over your funds. Combining an extendable authentication system with authorities and a composable authorization system with permissions, Swig enables a host of deployments.
You can bundle Swig with MPC wallet providers such as Para, to extend their existing wallet as a service product, as well as use Swig alongside key management systems like Turnkey.(3) You can require a 2FA one-time password to approve transactions on Swig and you can even create roles on Swig for limiting spending limits on specific applications. Swig is flexible and allows safe user defaults to be put in place to protect your funds while allowing smooth interactions on chain.
With only a few lines of code, a developer can interact with a user's Swig, just like they request signatures from a user today. Going one step forward, a developer can request to take action on the user's behalf, the user can approve these granular actions once, and then never need to see a signature request again unless the app wants to update permissions. Swig also allows for embedded paymaster functionality, allowing applications to easily manage user gas costs, unlocking simple on-chain experiences that reduce friction.
For Developers
With Swig, cheap programmable wallets are here. A user only needs one Swig and they cost less than 30 cents to create. When using a Swig, there is only a slight impact on CU usage as we have written the Swig program in highly optimized Solana program code and using previously unexplored account structure and compute usage optimizations. With Swig, it won’t feel like there is anything in the way.
Getting Started With Swig
Swig is currently in early development, and we’re looking for builders who want to test it, provide feedback, and help shape its future. If you’re a developer interested in experimenting with Swig, we’d love to hear from you.
If you are interested in building with Swig, please connect with us by emailing info@anagram.xyz.
We are also looking for team members to join us to contribute to Swig both on the business and engineering side. We'd love to talk to you if you're interested, dm us on X @anagramxyz or email us at talent@anagram.xyz
Swig is built for the future of crypto wallets. If you’re building with Solana, Ethereum, or both—now is the time to start exploring what’s possible!
(1) Anagram Ltd. and its affiliates may consult, invest, build, or otherwise have interest in companies or projects that are written about in this space. This content is for educational purposes only and does not constitute advice, marketing or solicitation for funding. Please see the disclaimer below for more information.
(2) Glider is a subsidiary of Anagram Ltd.
(3) Anagram Ltd. and its affiliates may consult, invest, build, or otherwise have interest in companies or projects that are written about in this space. This content is for educational purposes only and does not constitute advice, marketing or solicitation for funding. Please see the disclaimer below for more information.
LEGAL DISCLAIMER
The information in this article has been prepared by Anagram Ltd. (“Anagram”) for educational and informational purposes only. Under no circumstances should this, or any post on this website, be construed as solicitation for investment in Anagram, its affiliates, or any projects named herein or otherwise. The contents herein, and content available on any associated distribution platforms, including Anagram online social media accounts, should not be construed as or relied upon as investment, legal, tax, or other advice.
Certain information contained herein, including in charts and graphics, may have been obtained from third parties. While such sources are believed to be reliable, Anagram does not assume any responsibility for the accuracy or completeness of such information. No assurance is made by Anagram regarding the accuracy or completeness of the information or opinions set forth herein, whether or not obtained from third parties, and Anagram shall not be liable therefor. Certain statements herein are based on subjective beliefs, may differ from the views of other market participants, and are subject to change.
This presentation contains “forward-looking statements,” which can be identified by the use of forward-looking terminology such as “may”, “will”, “should”, “expect”, “anticipate”, “project”, “estimate”, “intend”, “continue” or “believe” or the negatives thereof or other variations thereon or comparable terminology. Due to various risks and uncertainties, actual events or results may differ materially and adversely from those reflected or contemplated in the forward-looking statements.