6 stable releases

2.0.6 Jan 6, 2025
2.0.5 Jun 21, 2024
2.0.4 May 7, 2024
2.0.3 Oct 24, 2023
2.0.1 Sep 11, 2023

#72 in #account

Download history 217/week @ 2024-12-09 208/week @ 2024-12-16 206/week @ 2024-12-23 176/week @ 2024-12-30 312/week @ 2025-01-06 186/week @ 2025-01-13 145/week @ 2025-01-20 90/week @ 2025-01-27 97/week @ 2025-02-03 72/week @ 2025-02-10 117/week @ 2025-02-17 182/week @ 2025-02-24 130/week @ 2025-03-03 122/week @ 2025-03-10 125/week @ 2025-03-17 84/week @ 2025-03-24

485 downloads per month
Used in bolt-lang

GPL-3.0-or-later

11KB
169 lines

GPL Session

Manage sessions in your Solana Anchor Programs.

Installation

cargo add session-keys --features no-entrypoint

Usage

  1. Import the dependencies
use session_keys::{SessionError, SessionToken, session_auth_or, Session};
  1. Derive the Session trait on your instruction struct
#[derive(Accounts, Session)]
pub struct Instruction<'info> {
    .....
    pub user: Account<'info, User>,

    #[session(
        // The ephemeral keypair signing the transaction
        signer = signer,
        // The authority of the user account which must have created the session
        authority = user.authority.key()
    )]
    // Session Tokens are passed as optional accounts
    pub session_token: Option<Account<'info, SessionToken>>,

    #[account(mut)]
    pub signer: Signer<'info>,
    .....
}
  1. Add the session_auth_or macro to your instruction handler with fallback logic on who the instruction should validate the signer when sessions are not present and an appropirate ErrorCode. If you've used require*! macros in anchor_lang you already know how this works.
#[session_auth_or(
    ctx.accounts.user.authority.key() == ctx.accounts.authority.key(),
    ErrorCode
)]
pub fn ix_handler(ctx: Context<Instruction>,) -> Result<()> {
.....
}

Example

See KamikazeJoe for an example of a game using session-keys.

Dependencies

~19–28MB
~489K SLoC