Skip to content

Mention that transactions with InvokeHostFunctionOp can't have memo or muxed account set #2263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sisuresh merged 1 commit into from
Feb 19, 2026
Merged

Mention that transactions with InvokeHostFunctionOp can't have memo or muxed account set #2263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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].
Expand Down