Our Solana Policy Engine is live!

While our architecture has always supported Solana, through our chain-agnostic infrastructure design, we’re excited to announce deeper protocol support that makes building on Solana even easier.

Now, with the launch of our Solana Policy Engine, you can write granular policies around transaction amounts, addresses, and program interactions using Turnkey’s API – making your Solana wallet implementation even more powerful and secure.

What’s a policy?

Turnkey’s policy engine is the foundation for flexible controls and permissions within every organization. Anyone using Turnkey can create a policy to allow or deny specific onchain transactions in combination, making it perfect for teams building consumer applications or infrastructure that handle sensitive transactions or transactions of size. Read on below to learn more about what you can build with policies and how they can serve your integration.

What can I do with policies?

Policies are inherently flexible and can be used for a wide variety of use cases. The following types of policies are just some examples for policies that you can create with both our Ethereum and Solana policy engines:

• Allow Solana transactions that include a transfer from one specific sender: Want users to only send funds from their hot wallet and not their cold wallet? Specify and allow transactions from only a single sender with a policy.

• Allow Solana transactions that include a transfer to only one specific recipient: Set up an “allowlist” to ensure funds are only able to be sent to known recipients.

• Allow Solana transactions that have exactly one transfer, to one specific recipient: Only allow one specific transaction to be sent to a specific recipient, enabling automated processing of specific one-time transactions without requiring broader permissions to be shared.

• Deny all Solana transactions transferring to an undesired address: Say you don’t want funds sent to a non-wallet contract address. Deny all transactions going to a specific address with ease.

You can take a look at the links above to access specific code examples for those policies (and more!).

Let’s get technical: How does the Turnkey Solana policy engine work?

Previously, all transaction types for Solana on Turnkey were signed using the SIGN_RAW_PAYLOAD  type in our API. With the Solana Policy Engine, you can now use the SIGN_TRANSACTION type, which gives you the ability to parse basic transaction metadata such as the following:

• All Accounts included

• All programs invoked

• All SOL Transfers in the Transaction, with Sender, Recipient Amounts

• All instruction call data within the transaction

As part of our commitment to open source and supporting the Solana ecosystem, we’ve also open-sourced our Solana transaction parser. This library contains tools to parse and inspect Solana transactions at the most primitive level, supporting both message-only and full transaction parsing. It’s designed to be a foundational tool for the Solana ecosystem, allowing developers to inspect transaction metadata, account interactions, and transfer details with precision.

This parser is an example of Turnkey’s infrastructure-first approach: we built robust, low-level tools that can be used by anyone in the ecosystem. By expanding parser support to include Solana and SVM transactions, we’re laying the groundwork for similar support across other chains, such as Cosmos and Bitcoin. To read more about additional chain support, you can check out our documentation here.

Build innovative experiences with policies

We’d love to see you build new onchain experiences with Solana policies. From DeFi, to payments, to in-app quests, policies can help you craft a better user experience by ensuring that user and team funds are safe with simple onchain logic.

If you’re a builder on Solana, you’re already eligible for $400 off the first month of your Pro Tier. Just shoot us an email at hello@turnkey.com with the email you used to sign up for Turnkey, and retweet this tweet to be eligible.