Sessions

​

Introduction

• Use when: an app needs repeated operations without prompting the original signer each time.
• For: interactive apps and services with time-limited delegated access.

​

How it works

1. Add a session-capable authority with a maximum duration and scoped permissions.
2. Have the original authority approve a temporary key and a duration within that maximum.
3. Use the temporary key to sign operations through the same role.
4. Let the session expire, replace it through the original authority, or remove its role to revoke access.

​

Session authorities

• Durations and expiry use slots. Choose a positive duration within the configured maximum.
• A session shares the role’s permissions and remaining budget. Opening a new session does not reset spending limits.
• Adding a session-capable role alone does not activate a session.

​

SDK example

​

Open a session

import {
  type Connection,
  type Keypair,
  type PublicKey,
  Transaction,
  sendAndConfirmTransaction,
} from "@solana/web3.js";
import { fetchSwig, getCreateSessionInstructions } from "@swig-wallet/classic";

async function openSession(
  connection: Connection,
  configAddress: PublicKey,
  owner: Keypair,
  roleId: number,
  sessionKey: Keypair,
) {
  const swig = await fetchSwig(connection, configAddress);
  const instructions = await getCreateSessionInstructions(
    swig,
    roleId,
    sessionKey.publicKey,
    500n,
    { payer: owner.publicKey },
  );
  return sendAndConfirmTransaction(
    connection,
    new Transaction().add(...instructions),
    [owner],
    { commitment: "confirmed" },
  );
}

​

Use the session

1. Refetch the wallet after confirmation.
2. Locate the role with findRoleBySessionKey(sessionKey.publicKey).
3. Pass that role ID to Signing.
4. Sign with sessionKey and the payer, then send the transaction.