Skip to content

Comments

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

Merged
sisuresh merged 1 commit intostellar:mainfrom
sisuresh:memo
Feb 19, 2026
Merged

Mention that transactions with InvokeHostFunctionOp can't have memo or muxed account set#2263
sisuresh merged 1 commit intostellar:mainfrom
sisuresh:memo

Conversation

@sisuresh
Copy link
Contributor

No description provided.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Soroban contract interaction docs to explicitly document transaction-level constraints when using InvokeHostFunctionOp, helping developers avoid constructing invalid transactions.

Changes:

  • Documented that transactions containing InvokeHostFunctionOp must use MEMO_NONE.
  • Documented that muxed accounts are not allowed as the transaction source account.
  • Documented that muxed accounts are not allowed as the operation source account (if set).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@stellar-jenkins
Copy link

@stellar-jenkins
Copy link

@sisuresh sisuresh merged commit dac6e3a into stellar:main Feb 19, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants