Standalone applications
Until the user connects, onlyeth_requestAccounts, wallet_connect, wallet_sendCalls, eth_accounts, eth_chainId, and net_version are served. The other methods on this page, apart from wallet_getCallsStatus, throw 4100. Connect first.
Answered locally by the SDK. No popup, no user interaction.
Served by the Startale App popup. These prompt the user.
Not served. These requests fail.
eth_signTypedData_v1, eth_signTypedData_v3, eth_signTypedData (unversioned), eth_signTransaction, eth_ecRecover, personal_ecRecover, wallet_addEthereumChain, wallet_watchAsset, wallet_grantPermissions, wallet_showCallsStatus open the Startale App popup, which shows the method as not supported. Closing it rejects the request with 4001, not 4200, so do not treat every 4001 as the user declining a supported action.
wallet_getCallsStatus never reaches the Startale App and is not supported. Do not call it.
Inside a Mini App
The surface is deliberately narrower. Anything not listed throws4200 Unsupported method.
See Mini App wallet integration for the full constraint surface, including why signing from a linked EOA is not possible.
Batch status is not pollable
Neitherwallet_getCallsStatus nor wallet_showCallsStatus is implemented in either context. wallet_sendCalls resolves with transactionHash and userOpHash once the batch is submitted. If you need a receipt, look it up with your own RPC client.
Related
Errors
The error codes these methods throw.
Mini App wallet integration
The narrowed surface, and why.