Use a session

Installing sessions

To enable a session: Examples on this page use @rhinestone/sdk, where rhinestone is the RhinestoneSDK instance from Create a session with a custom setup.

import { enableSession } from "@rhinestone/sdk/actions/smart-sessions";

const sessions = [session];
const sessionDetails = await rhinestoneAccount.getSessionDetails(sessions);
const enableSignature =
  await rhinestoneAccount.signEnableSession(sessionDetails);
const sessionIndex = 0;

const transaction = await rhinestoneAccount.prepareTransaction({
  destination: {
    chain,
    calls: [
      enableSession(
        session,
        enableSignature,
        sessionDetails.hashesAndChainIds,
        sessionIndex,
      ),
    ],
  },
  sponsored: true,
});

Pass the Session that createSession returned, or the one you stored; do not rebuild it from its definition. These no-delivery examples require fee and gas sponsorship. chain must match the session’s chain. Sign and submit enable/disable transactions with the account owner; the transfer example assumes the account already holds USDC. You can also enable a session with a signature. See Multi-chain sessions for details.

Re-enable a session with a lifetime budget

A permit’s maxAmount without oneTimeUse is a lifetime budget (session.lifetimeBudget). Enabling the session again while it is already enabled resets that budget, so getSessionDetails refuses such a session:

The session <permissionId> is already enabled on chain <chainId>, and its maxAmount is a lifetime budget: signing its enable again would reset that budget. Leave it out of getSessionDetails, or pass { allowBudgetReset: true } to reset it.

Leave enabled sessions out of getSessionDetails. Pass allowBudgetReset only when you intend to give the session a fresh budget:

const sessionDetails = await rhinestoneAccount.getSessionDetails(sessions, {
  allowBudgetReset: true,
});

Disabling a session and enabling it again also starts a fresh budget.

Checking session status

To check if a session is enabled:

const isEnabled = await rhinestoneAccount.isSessionEnabled(session);

Using sessions

To authorize a transaction with a session key you’ve enabled before:

const prepared = await rhinestoneAccount.prepareTransaction({
  destination: {
    chain,
    calls: [
      {
        to: usdcAddress,
        data: encodeFunctionData({
          abi: erc20Abi,
          functionName: "transfer",
          args: ["0xd8da6bf26964af9d7eed9e03e53415d37aa96045", 1n],
        }),
      },
    ],
  },
  sponsored: true,
  signers: {
    type: "session",
    session,
  },
});
const signed = await rhinestoneAccount.signTransaction(prepared);
const transactionResult = await rhinestoneAccount.submitTransaction(signed);

This will prompt the signature request from the session owner(s) and submit the transaction on their behalf. A session scoped by a cross-chain permit settles only sponsored intents without an app fee unless the permit sets allowFees.

You can also enable and use the session key in one transaction with the enable mode.

Disabling a session

To disable a single enabled session, use disableSession. This only removes a single session: to uninstall the validator entirely (and every session with it), use disable instead.

import { disableSession } from "@rhinestone/sdk/actions/smart-sessions";

const transaction = await rhinestoneAccount.prepareTransaction({
  destination: { chain, calls: [disableSession(session)] },
  sponsored: true,
});

Embedded wallet

Custom setup

Installing sessions

Re-enable a session with a lifetime budget

Checking session status

Using sessions

Disabling a session

​Installing sessions

​Re-enable a session with a lifetime budget

​Checking session status

​Using sessions

​Disabling a session

Installing sessions

Re-enable a session with a lifetime budget

Checking session status

Using sessions

Disabling a session