Smart accounts on Soneium do not need users to hold native ETH to transact. Gas is paid by a paymaster that co-signs each UserOperation. Whether your users see a gasless flow depends on where the transaction is signed and which paymaster you wire into the SDK.Documentation Index
Fetch the complete documentation index at: https://docs.startale.com/llms.txt
Use this file to discover all available pages before exploring further.
The two-tier sponsorship model
Tier 1, inside the Startale App. Transactions that originate from a Mini App running inside the Startale App host are sponsored by Startale’s host paymaster. Mini App developers do not configure anything; gas is invisible to the user and to your code. Tier 2, standalone dApps. When your app integrates@startale/app-sdk outside of the Startale App (a normal website, a desktop app, a mobile webview), Startale does not sponsor gas for your transactions. You either:
- Configure your own paymaster through
paymasterOptions(recommended), or - Let the user pay gas out of their smart account’s ETH balance.
This is the intended model. If you are seeing legacy behavior where a standalone dApp’s gas is silently sponsored, treat it as transitional. Build against the model documented here so you do not have to migrate later.
Who pays in each context
| Context | Sponsored by Startale | Bring your own paymaster | User pays |
|---|---|---|---|
| Mini App inside the Startale App | yes | no | no |
| In-app actions (swaps, transfers in the Startale App itself) | yes | no | no |
Standalone dApp using @startale/app-sdk, with paymasterOptions configured | no | yes | no |
Standalone dApp using @startale/app-sdk, with no paymaster | no | no | yes |
Backend service using @startale-scs/aa-sdk directly | no | yes | yes |
How the paymasters fit together
The App SDK and the AA SDK target the same infrastructure. The App SDK is a higher-level wrapper that ultimately produces ERC-4337 UserOperations and forwards them to a paymaster. The AA SDK is the lower-level toolkit you would use to build a paymaster service or to integrate AA without the host popup. The takeaway: the App SDK lets you point at any ERC-7677 paymaster service. The simplest production path is to provision an SCS paymaster (managed or self-funded) and pass its URL andpaymasterId through paymasterOptions. You can also self-host an ERC-7677 service if you need custom rules.
Deciding what to do
I am building a Mini App
Do nothing. Gas is sponsored by the host.
I am building a standalone dApp
Configure
paymasterOptions with an SCS paymaster, or accept that users pay gas.I want fine-grained sponsorship rules
Run an ERC-7677 service that sponsors selectively (per user, per call, per policy).
I am working at the AA layer
Use the AA SDK directly with the SCS paymaster. The App SDK is built on this.
Networks
Both Soneium Mainnet and Soneium Minato run EntryPoint v0.7. The same paymaster RPC handles both networks; you select the network with the chain id passed to the SDK.| Network | Chain ID | Default sponsorship in Mini App |
|---|---|---|
| Soneium Mainnet | 1868 | yes |
| Soneium Minato | 1946 | yes |
Related
App SDK gasless reference
The exact code paths for sponsored, custom-paymaster, and user-pays flows.
Custom paymaster
Wire an SCS paymaster or your own ERC-7677 service into the App SDK.
AA SDK paymaster modes
Provision a managed or self-funded paymaster in the SCS Portal.
ERC-20 paymaster
Charge gas in a token instead of native ETH.