Solana Protocol SDK

Introduction

• Use when: you want to control wallet creation, authorization, and transaction submission in your application.
• For: developers integrating wallets into apps, payment flows, and automated services.

How it works

1. Create a wallet and keep its config address and asset-holding wallet address.
2. Give each signer a role: an authority identifies who can approve; permissions define what it can do.
3. Build the instructions for a transfer, swap, or other wallet action.
4. Authorize with the selected role, sign the Solana transaction, then submit and confirm it.

Wallet structure

Flow

Wallet role
├─ Authority approves
└─ Permissions apply
   ↓
Prepare instructions
   ↓
Sign → send → confirm

SDK example

npm install @swig-wallet/classic @solana/web3.js

cargo add swig-sdk swig-interface

• These TypeScript examples use Classic with Web3.js 1.x. Solana Kit applications can use @swig-wallet/kit.
• Use a Solana RPC connection, a funded fee payer, and a compatible Swig deployment.
• Start with Create a wallet, or derive an address first with Counterfactual creation.

Authorities

Permissions and transactions

• Choose spending limits, program access, and administrative permissions.
• Grant authorization lock permission to hold, capture, and release funds.
• Add a role or remove a role as access changes.
• Authorize instructions, then send the transaction.

Use cases

• Transfers: send SOL or tokens.
• Swaps: trade wallet-owned assets.
• Recovery: replace a lost signer through a guardian.