session must be a resolved Session (the return value of
toSession(...)). Re-resolving it here would drop the explicit
permissions — a Session only carries the derived actions, not the
original SessionDefinition.permissions — which makes the on-chain digest
computed by SmartSessionLens.getAndVerifyDigest diverge from the one
signed in getSessionDetails, causing the emissary to reject the enable.
Import
Usage
Parameters
Session
required
resolved session to enable
`0x${string}`
required
{ chainId: bigint; sessionDigest: `0x${string}` }[]
required
number
required
Returns
LazyCallInput
Calls to enable the smart session