mvx_sharp_edges

MultiversX smart contract async callbacks fail when the original asynchronous call encounters an out-of-gas error or executes on a different shard, causing unexpected state mutations if not handled defensively.

Handling out-of-gas errors in cross-shard transactions on MultiversX requires recognizing that the asynchronous call mechanism may silently fail, making defensive state checks within callbacks essential to prevent contract corruption.

The difference between Vec and VecMapper in MultiversX smart contract storage lies in gas consumption and memory handling, where VecMapper prevents the severe gas and memory issues associated with standard Vec operations.

Managing state during a MultiversX contract upgrade requires understanding initialization logic and state management quirks to ensure existing storage mappers and ESDT token precision are not corrupted during the upgradeability process.

Ensuring correct ESDT decimal precision in MultiversX smart contracts requires strict handling of decimal places during token transfers and storage to avoid calculation bugs and value mismatches within the WASM runtime.

Common MultiversX WASM runtime quirks include non-obvious behaviors in gas limit handling, storage mapper performance degradation, and asynchronous call failures that can introduce subtle bugs into smart contract execution.