docs: add Common Pitfalls section to MASM index#341
Open
pplmaverick wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Common Pitfalls section to the MASM smart contracts index page covering
two undocumented traps encountered during dApp development:
Procedure hash byte order: MASP inspector output is big-endian per 8-byte chunk,
but call.0xHEX requires little-endian per chunk. Includes a Python conversion snippet.
Related: docs: MASP inspector proc hash requires per-chunk byte-reversal before use in call.0xHEX compiler#1267
call vs exec stack depth: calling a Felt-returning procedure via call.0xPROC_HASH
triggers InvalidStackDepthOnReturn { depth: 17 }. Workaround is exec + void redesign.
Related: New compiler(next)breaks miden-client exec and call - "stack depth must be 16, was 17" compiler#1192