Bridge funds first, then deploy a smart account on Mantle

A smart account on Mantle can be funded through a bridge before its contract is deployed, provided the funds reach the account’s intended Mantle address. A wallet factory derives that address from the account’s setup, and a first transaction can deploy the contract there. The bridge moves assets between networks; it does not deploy the account. For the bridge steps and fee trade-offs, see this mantle bridge guide.

How can bridge funds reach an account that is not deployed?

A smart account can have a known address before it has contract code. Many account systems calculate that address from the owner or signers, the chosen account implementation, and a factory’s deployment rules. On Mantle, the address can receive assets even while the contract is absent, much as a numbered mailbox can be assigned before it is installed.

The important condition is that the address be calculated for the right network and account setup. A different factory, owner, implementation or configuration can produce a different address. Confirm the destination in the smart account wallet before bridging, and check that the bridge’s receiving-address field actually lets you send to it. Some bridge flows default to the connected source wallet’s address.

What happens when the smart account is deployed?

In a common ERC-4337 flow, the wallet prepares a signed user operation describing the action the account should take. If the account does not yet exist, the operation includes deployment data for a factory. A bundler checks the operation, then submits it through the chain’s EntryPoint contract. The factory creates the account, and the EntryPoint processes its requested action if validation succeeds.

That first action could be a simple transfer or another supported call. Deployment and the first action can therefore happen in one operation, rather than requiring a separate manual deployment transaction. The account’s owner or configured signers authorize the operation; the factory supplies the code and creates the account at its derived address.

Should you bridge before or after deployment?

Bridging to the undeployed address can save a step: once funds arrive on Mantle, the first authorized operation can deploy the account and use them. But this depends on the bridge accepting that destination and the wallet and bundler supporting deployment on first use. Funds arriving at an address do not guarantee that every wallet interface can control or spend them.

Bridging to an existing wallet first is easier to inspect, but it adds a transfer on Mantle from that wallet to the smart account. That transfer needs a signer-controlled account and enough network gas. In either route, plan for deployment and later transactions to pay network fees. A paymaster may sponsor fees when the wallet supports one and its conditions are met; that is a separate service, not a property of the bridge.

• Generate the account address using the exact wallet, owner and setup you intend to use on Mantle.
• Check whether the bridge can send to that address, and confirm the network and asset shown at the destination.
• Leave enough of the accepted fee asset for the first operation, unless a supported paymaster will cover it.
• After the bridge completes, verify the destination balance and account deployment status before signing the first operation.

The order is simple: derive and verify the address, bridge to it if the route supports that recipient, then deploy through an authorized first operation. What changes at deployment is that the address gains executable account code; next, check that the bridge transfer settled and that the wallet can submit an operation with the available funds and fee setup.