Connecting a wallet to an application today means giving that application access for as long as you forget to revoke it. Session credentials change that by issuing authorization that is scoped to specific actions, bounded by time, and revocable without affecting anything else.
The way most wallets handle application authorization today is a binary decision with a long tail. You connect your wallet to an application, the application gets signing access, and that access persists until you manually revoke it — which most users never do, because most wallet interfaces make revocation a secondary concern that requires navigating several menus to find. The result is a growing list of applications that have indefinite access to sign transactions from an account, most of which the user forgot they connected in the first place.
This is not a theoretical security concern. Applications change hands, get compromised, or simply behave differently over time than they did when the user first connected. An application that had legitimate access to a wallet six months ago may not be one the user would grant access to today if asked again. But the wallet has no mechanism to expire that access automatically or to limit what the application was allowed to do in the first place. The authorization model is connect-and-forget, which puts the entire burden of ongoing access management on the user’s memory.
Thanos Wallet is being built toward session credentials as the replacement for this model. A session credential is not a blanket grant of wallet access — it is a structured authorization that specifies what an application is allowed to do, for how long, and under what conditions. An application granted a session credential to manage a specific yield position is authorized to interact with the contracts relevant to that position during the session period. It is not authorized to move other assets, interact with other contracts, or continue operating after the session expires.
The practical difference is that session credentials make authorization legible and bounded rather than implicit and open-ended. A user granting a session credential knows what they are authorizing, for how long, and what the revocation path is. An application operating under a session credential cannot gradually expand its access over time by relying on an authorization that was never designed to be specific. When the session ends — because it expired, because the user revoked it, or because the conditions that permitted it no longer apply — the access ends with it, without requiring the user to remember that the connection existed.
This model also makes Thanos Wallet more useful in the context of autonomous agents and multi-application workflows. When an agent or an application needs to act on behalf of a user, the session credential defines the exact scope of that permission. The agent can do what it was authorized to do. It cannot do more. The credential carries the boundary as a property of the authorization itself, not as a convention that relies on the application choosing to respect limits that were never actually enforced.
Most wallets do not offer this because they were designed around a simpler interaction model — one user, one connection decision, one level of access. That model is increasingly inadequate for an ecosystem where applications are numerous, agents are active, and the authorization surface of a single wallet account can span dozens of connected services at once. Thanos Wallet’s session credential architecture is built for that reality: not by making access harder to grant, but by making it specific enough that granting it does not require trusting every future behavior of everything you ever connect to.
