Send a transaction the same way you would with any wagmi-compatible wallet. The user’s smart account is the sender. For details on who pays gas and how to configure sponsorship, see Gas sponsorship.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.
Send native value
Call a contract
With the raw provider
from field is set automatically to the user’s smart account. If you supply a from value, it is ignored.
How gas works in Mini Apps
When your Mini App runs inside the Startale App, everyeth_sendTransaction call is gasless for the user. Here is exactly what happens under the hood:
- Context detection. The App SDK detects it is running inside the Startale App iframe and automatically routes requests through the host wallet instead of opening a standalone popup.
-
Conversion to a UserOperation. The SDK converts the
eth_sendTransactioncall into an ERC-4337 UserOperation using the AA SDK. This is what allows the transaction to carry a paymaster signature. -
Paymaster capability injection. Before the request reaches the wallet, the SDK automatically injects an EIP-5792
paymasterServicecapability into thewallet_sendCallspayload:This happens in the SDK’s request interceptor — your code does not need to pass any paymaster configuration. -
AA SDK builds and signs the UserOperation. The Startale App’s backend uses
createSCSPaymasterClientfrom the AA SDK to fetch a paymaster signature for the UserOperation. The paymaster co-signs the UserOp, committing to cover the gas cost. -
Bundler submission. The signed UserOperation is submitted to the SCS Bundler, which packages it and calls
handleOpson the EntryPoint contract. Gas is paid by the Startale paymaster, not the user.
paymasterOptions, no paymaster URL, and no paymasterId in your code. The Startale App host owns the paymaster and injects it transparently.
For standalone dApps outside the Startale App, gas sponsorship requires explicit configuration. See Gas sponsorship for the full breakdown and the paymasterOptions reference.
For batched calls or atomic multi-step transactions, see Batched calls.
Errors
| Code | Meaning |
|---|---|
4001 | User rejected the transaction in the popup |
4100 | Wallet not connected |
4900 | Provider disconnected |