controller-sessions

Gasless transactions for web3 controllers are enabled by defining a policy set for your application and initializing the Cartridge Controller with those session policies to pre-approve contract interactions.

Session policies in web3 authorization define contract permissions, granted methods, token spending limits, and signed message rules to enable secure, pre-approved interactions without repetitive user prompts.

You configure spending limits for pre-approved contract interactions by defining token spending rules within your SessionPolicies, enforcing secure transaction limits across the session lifecycle for the Cartridge Controller.

Yes, you can customize error display modes for web3 session policies. The configuration supports robust error handling across session lifecycles, allowing configurable display modes for Controller integrations during verified sessions.

You need verified sessions for controller integrations when your application requires trusted flows with pre-approved contract interaction policies, signed message policies, and enforced spending limits to minimize transaction prompts.