Custom transaction

Introduction

A custom transaction executes your Solana instructions through an existing Swig wallet. Use it to integrate a program that the transfer and swap helpers do not cover. The acting role’s program and asset permissions still apply. The backend prepares the transaction; your application reviews, signs, and submits it. Use the Protocol SDK for direct instruction construction.

SDK examples

Prepare custom instructions

Use a wallet handle with its requester authority in TypeScript/Python, or WalletClient in Rust. See Client setup.

const prepared = await wallet.buildTransaction({
  feePayer,
  instructions: [
    {
      programId: targetProgramId,
      accounts: [
        {
          pubkey: writableAccount,
          isWritable: true,
        },
        {
          pubkey: readonlyAccount,
        },
      ],
      data: Buffer.from(instructionData).toString('base64'),
    },
  ],
  addressLookupTableAccounts: [lookupTableAddress],
});

from swig_developer_sdk import SolanaAccountMeta, SolanaInstructionInput

prepared = await wallet.build_transaction(
    fee_payer=fee_payer,
    instructions=(
        SolanaInstructionInput(
            program_id=target_program_id,
            accounts=(
                SolanaAccountMeta(
                    pubkey=writable_account,
                    is_writable=True,
                ),
                SolanaAccountMeta(pubkey=readonly_account),
            ),
            data=instruction_data,
        ),
    ),
    address_lookup_table_accounts=(lookup_table_address,),
)

use swig_developer_sdk::{AccountMeta, Instruction, PrepareTransactionArgs};

let prepared = wallet
    .prepare_transaction(PrepareTransactionArgs {
        swig_config_address,
        fee_payer,
        requester_authority: requester_authority.clone(),
        instructions: vec![Instruction {
            program_id: target_program_id,
            accounts: vec![
                AccountMeta::new(writable_account, false),
                AccountMeta::new_readonly(readonly_account, false),
            ],
            data: instruction_data,
        }],
        address_lookup_table_accounts: vec![lookup_table_address],
    })
    .await?;

Review the returned transaction and complete Signing. ParticipantSet operations first need approval compilation. An empty embedded-signature list does not remove native Ed25519 signer requirements.

Input

Parameter	Required	Description
Wallet config address and network	Yes	Bind through the configured wallet client
Requester authority	Yes	Ed25519, secp256r1, or ParticipantSet authority
`feePayer` / `fee_payer`	Yes	Public key paying the transaction fee
`instructions`	Yes	Nonempty ordered list of program IDs, account metadata, and instruction data
Account metadata	For each instruction	Public key and signer/writable flags
`addressLookupTableAccounts` / `address_lookup_table_accounts`	No	Distinct lookup-table addresses; must be empty for ParticipantSet requests

A signer account must be the derived Swig wallet address, fee payer, or Ed25519 requester. TypeScript accepts base64 instruction data; Python and Rust examples use bytes. Rust uses native Instruction and AccountMeta values.

Errors

Error	Meaning
Invalid instruction input	The instruction list is empty or its account metadata is unsupported. Supply instructions with valid program IDs, data, and permitted signer accounts.
Unsupported lookup-table use	A ParticipantSet requester includes address lookup tables. Keep the lookup-table list empty for that requester.
Permission check fails	The operation exceeds the acting role’s program or asset grants. Inspect the target program, asset amount, and role permissions before signing.

Getting started

Wallet

Query

Finance

AI

Additional resources