From e311b18553d0ca3400530cbe18b09afaccf68d8d Mon Sep 17 00:00:00 2001 From: Siddharth Suresh Date: Wed, 18 Feb 2026 17:02:32 -0800 Subject: [PATCH] Mention that transactions with InvokeHostFunctionOp can't have memo set --- .../contract-interactions/stellar-transaction.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx index ac8d0bcdfc..c938b71eb0 100644 --- a/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx +++ b/docs/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx @@ -343,6 +343,14 @@ The `InvokeHostFunctionOp` can be used to perform the following Soroban operatio There is only a single `InvokeHostFunctionOp` allowed per transaction. Contracts should be used to perform multiple actions atomically, for example, to deploy a new contract and initialize it atomically. +Additionally, Soroban transactions containing `InvokeHostFunctionOp` have the following restrictions: + +- The transaction **cannot include a memo** — the memo must be set to `MEMO_NONE`. +- The transaction **source account cannot be a muxed account**. +- The **operation source account, if set, cannot be a muxed account**. + +See [Send to and receive payments from Contract Accounts](../../../../build/guides/transactions/send-and-receive-c-accounts.mdx) for information on how to provide a muxed ID when making payments in Soroban. + ### InvokeHostFunctionOp The XDR of `HostFunction` and `InvokeHostFunctionOp` below can be found [here][xdr].