Skip to main content
The SDK handles the account deployments for you. When transacting on a new chain for the first time, the account will be deployed as part of the intent. The Orchestrator automatically detects if the account needs to be deployed, then passes the init data to the relayer market as part of the intent, which is then executed by a relayer.

​
How deployment works

Deployment is per-chain. When you submit a transaction targeting a chain where the account is not deployed yet, the Orchestrator bundles the deployment into the intent automatically. The account is only deployed on that specific chain, not on all supported chains at once. Receiving tokens at the counterfactual address does not trigger deployment. Only an outbound transaction submitted through the SDK does.

​
Who pays for deployment?

Developer sponsorship and the user’s account balance are separate. Sponsorship is a developer-funded deposit that subsidises fees on behalf of users. The user’s account balance is whatever tokens the user holds. See Gas and fee sponsorship for setup details.
You can make deployment completely gasless for the user with sponsorships.
Otherwise, the user needs to have some tokens on either the chain you’re deploying to, or any other supported chain (provided the account is already deployed there).

​
Check Status

You can check if the account is deployed on a specific chain:

​
Manual Deployments

You can manually trigger an account deployment on any chain:
You can also sponsor the gas:

​
Deploy from Another Account

You can deploy an account from another smart account using the deploy action. This can be useful when you want to pay for a deployment with another account: