multiversx-sharp-edges

MultiversX async callbacks can trigger state reverts due to non-obvious platform behaviors and pending callback tracking issues. This catalog identifies these async boundary quirks and offers solutions to prevent unexpected state changes and cache invalidation during contract execution.

Common MultiversX storage mapper gotchas involve VecMapper indexing offsets, MapMapper memory model overhead, and storage key collisions. Reviewing these platform-specific behaviors helps prevent data corruption and optimize gas limits during smart contract debugging.

Preventing rounding attack vectors and token decimal precision errors in MultiversX dApps requires understanding NonZeroBigUint in payments and EGLD/ESDT transfer behaviors. This Skill highlights these subtle vulnerabilities to secure your smart contracts.

Choosing between require vs sc_panic in MultiversX smart contracts impacts error handling and backtransfers accumulation during security audits. This catalog explains the distinct behaviors of each method to help you avoid common pitfalls and secure contract upgradeability.

Block info in MultiversX view functions exhibits non-obvious behaviors compared to regular calls, which can lead to unexpected logic errors. This Skill documents these platform-specific quirks to ensure accurate data retrieval during code reviews and debugging.

MultiversX upgradeability pitfalls often involve storage key collisions and cache invalidation across async boundaries after contract updates. This catalog provides a comprehensive checklist to identify these known limitations and secure your dApps during migration.