Skip to main content
Relaying lets your application submit authorized transactions without operating its own transaction-sending infrastructure. Your application defines the actions, the account’s signer approves them, and Rhinestone coordinates their onchain execution. Use relaying for transfers and contract interactions on a single chain. When an action needs funds from another chain, use Multichain transactions.

​
Execute calls and deploy accounts

Embedded wallets and custom signers can relay one or more contract calls. Calls in the same batch execute in order and revert together if one fails, supporting actions such as approving a token and depositing it in a single transaction. For a new smart account, the first transaction can include deployment on the execution chain. You do not need to deploy the account separately before users interact with your application. Deployment is per chain; creating an account or sending assets to its address does not deploy its contract. Existing Safes can also relay owner-signed native Safe transactions through a separate API, without converting them into SDK intents.

​
Fees and execution status

Relaying separates transaction authorization from gas payment. Your application can sponsor fees, or use the supported user-paid flow. Sponsorship covers the configured fees, not the assets transferred or spent by the calls. An accepted submission is not confirmation that the transaction succeeded. Rhinestone provides status tracking and transaction hashes so your application can distinguish pending execution from a confirmed outcome before updating balances or retrying an action.

​
Get started