Skip to main content

​
The Problem with Web3 UX Today

In Web3 today, the user experience is often interrupted. Every swap, every listing, every minor action requires a wallet pop-up, forcing you to “sign” and approve. This creates friction and makes apps feel clunky compared to the smooth apps we use every day.

​
What Are Smart Sessions?

Smart Sessions is a solution to this problem. A Smart Session is a secure, temporary, and strictly limited set of permissions that you grant to an app. Instead of approving every single transaction, you approve a session once, allowing the app to perform a range of pre-agreed actions on your behalf. This eliminates constant pop-ups and unlocks a fluid, Web2-like experience without sacrificing security or self-custody.
💡 Think of it this way: It’s less like handing over your master key (your main wallet signer) and more like giving an application a special-purpose keycard with very clear rules and limitations.

​
Two Types of Smart Sessions

Sequence offers two distinct types of Smart Sessions, each designed for a different purpose:
  • Implicit Sessions: For ultimate convenience within a single, trusted app.
  • Explicit Sessions: For powerful, granular control over any on-chain action.

​
1. Implicit Sessions: The “In-App Convenience Pass”

An Implicit Session is the simplest and most common type of Smart Session. Its entire purpose is to make your experience inside a single app as smooth as possible.

​
🎯 The Core Idea

When you connect to an app you trust, you are creating a “trust boundary” around that app’s website domain. An Implicit Session gives that app a pass to operate freely only within its own walls.

​
⚙️ How It Works

  1. Connect & Trust: You connect your wallet to an app (e.g., app.my-defi-protocol.com)
  2. Silent Approval: A session is automatically and silently created that is cryptographically locked to that specific domain without the user having to approve it.
  3. Seamless Experience: You can now perform any action inside that app, swapping, staking, listing, without any further pop-ups. It just works.

​
🔒 The Security Guardrail

This session is useless anywhere else. If the app was malicious and tried to use this session to call a contract outside its domain (like the USDC contract), the transaction would be automatically rejected on-chain. The session is only valid for the app’s own smart contracts. The app will configure the permissions in the Sequence Builder
All transactions must be sponsored by the DApp itself when using Implicit Sessions since using any other currency as a fee option is treated as an external contract interaction and will be blocked.

​
📊 Implicit Sessions at a Glance

​
2. Explicit Sessions: The “Programmable Permission Slip”

An Explicit Session is a more advanced and powerful tool. It’s designed for when an app needs to perform very specific tasks that interact with other external protocols.

​
🎯 The Core Idea

Instead of trusting an app and its smart contracts only, you are approving a precise list of rules for a temporary signer that can interact with any smart contract. You are building a custom permission slip that says exactly what can be done, where it can be done, how much can be spent, for how long, and for which contracts.

​
⚙️ How It Works

  1. The app proposal: The app presents your wallet with a list of very specific permissions it needs. For example:
    • “Allow me to call the transfer function on the USDC contract.”
    • ”… with the recipient address 0x... only”
    • “…for a cumulative total of no more than 100 USDC.”
    • “…for a duration of 24 hours.”
  2. You Explicitly Approve the Rules: Your wallet displays these rules in a human-readable format. You review and approve this exact set of conditions.
  3. The app Executes: The app can now perform those actions automatically, with 0 pop-ups.

​
🔒 The Security Guardrail

The power of Explicit Sessions comes from their granularity. Each rule is validated on-chain. If the app tries to do anything outside the approved scope, like spend 101 USDC instead of 100, or call the approve function instead of transfer, the transaction will fail.

​
📊 Explicit Sessions at a Glance

​
Versatile Integrations

Best part is that you can combine the two types of sessions together to get the best of both worlds. Whenever you go out of scope on an Implicit Session, Sequence SDKs will automatically switch a single-transaction approval state, functioning like an EOA. For repeated actions outside of an Implicit Session, you can request an Explicit Session for a seamless integration.