Thyme Lift
Lift sponsors gas for authorized contract calls and submits ERC-4337 UserOperations. You choose which accounts and contract functions may receive sponsorship, then follow each authorization, transaction, and settlement in the Lift console.
An integration belongs to a workspace and project. Its server-side secret key authenticates your application. Each integration has policies containing sender, chain, contract, selector, and spending limits. An operation records a sponsorship request and its eventual outcome.
Current availability
The current runtime is an Ethereum Sepolia pilot. A configured endpoint or saved policy does not establish that sponsorship is enabled or funded.
| Capability | Current support |
|---|---|
| Chain | Ethereum Sepolia, chain ID 11155111, when enabled |
| EntryPoint | ERC-4337 v0.7 |
| Account | Already-deployed Safe 1.4.1 proxy using the pinned SafeL2 singleton and Safe4337Module 0.3.0 |
| Account configuration | The pinned Safe4337Module must be the only enabled module and the fallback handler |
| Calls | One canonical executeUserOp or executeUserOpWithErrorString call with operation = 0 |
| Call value | 0 native tokens |
| Account deployment, setup, batching, delegatecall | Unavailable through the public Lift API |
| Mainnet sponsorship | Unavailable in this pilot |
| Sepolia gas charge | Zero dBank; native gas usage is still tracked |
Safe7579 accounts and additional Safe modules are outside this public adapter. Keep the account's owner configuration fixed during the pilot. Chain names elsewhere in the console are a configuration catalog, not a promise of enabled sponsorship.
The pinned singleton is 0x29fcB43b46531BcA003ddC8FCB67FFE91900C762, and the Safe4337Module is 0x75cf11467937ce3F2f357CE24ffc3DBF8fD5c226. Lift verifies the deployed code and account configuration; matching the Safe version string alone is insufficient.
Where Lift fits
| Product | Responsibility |
|---|---|
| Flow | Runs your task, evaluates its result, and executes authorized calls using a profile |
| Gate | Provides execution RPC for chain reads, contract simulation, fee information, and transactions |
| Lift | Authorizes and sponsors supported UserOperations, submits them, and reconciles gas usage |
Lift's endpoint is not a general execution RPC. Use a separate Gate client for chain reads and fee estimation. Flow's supported Roles profiles use a managed Lift integration; task authors do not add Lift keys to task code.
Start here
- Connect your application with viem and permissionless.
- Configure policies and keys for your application's allowed calls.
- Use the JSON-RPC API and handle its errors and limits.
- Track operations and billing through inclusion, settlement, and finality.
- Understand Flow sponsorship and managed policies.