> For the complete documentation index, see [llms.txt](https://docs.sail.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sail.money/sailor/guides/deploy-sma.md). # Deploy & predict an SMA An SMA is a Safe registered with `SailKernel`, with the kernel enabled as a module. Sailor creates and tracks it in `.sail/account.json`. ## Predict the address first Because the kernel binds the [CREATE2 salt to the account's principals](/protocol/concepts/deterministic-deployment.md), you can compute the SMA address before deploying — and it's identical on every supported chain. ```bash sailor account predict # options: # --owner
owner EOA (defaults to .sail/account.json) # --manager
agent (manager) wallet, mixed into the kernel salt # --salt CREATE2 salt nonce (default: 0) # --chain show the prediction for one chain only # --json machine-readable output ``` The same owner + manager + salt produce the same address everywhere, so you can fund the address ahead of deployment. A different manager or salt lands at a different address (front-run resistance). ## Deploy ```bash sailor onboard --new-sma # options: # --sma
use a specific SMA instead of prompting # --new-sma create a new SMA via SailKernel # --salt CREATE2 salt (0 for your first SMA; increment for subsequent ones) # --template also register this permission (kind, label, or address) # --skip-mandate skip the permission-registration step # --json non-interactive JSON output ``` `onboard` walks the full setup: it creates the SMA on-chain (owner signs in the [signing server](/sailor/concepts/keys-and-custody.md)), optionally attaches a first mandate, and confirms the agent is operational. Owner-signed steps go through the browser; the agent submits what it's allowed to. ## Deploy the same address on another chain Once an SMA exists, replicate its address on another supported chain with the same principals: ```bash sailor account deploy-chain --chain 42161 # --chain is required # --salt defaults to the saltNonce stored in .sail/account.json # --json ``` See [Multi-chain operation](/sailor/guides/multi-chain.md). ## Inspect what you have ```bash sailor status # current account, permission, and session status sailor scan # discover the owner's SMAs + permissions + keys → context.json sailor doctor # read-only preflight: kernel model, permission health, RPC + gas balances ``` `doctor` is the right first call before spending gas — it reports the kernel's [dispatch model](/protocol/architecture/dispatch.md), permission health, RPC reachability, and gas balances. Next: [Build & register a mandate](/sailor/guides/build-a-mandate.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sail.money/sailor/guides/deploy-sma.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.