multiversx-cross-contract-storage

You can read another contract's storage directly by using the `storage_mapper_from_address` function. This bypasses async proxy calls for read-only state retrieval, reducing gas costs and complexity.

The best way to optimize gas for cross-contract reads is to use `storage_mapper_from_address` to access another same-shard contract's storage variables directly. This avoids the high gas overhead of traditional asynchronous view calls.

No, direct cross-contract storage reading works exclusively for same-shard contracts. You must ensure both the calling contract and the target contract reside in the same shard to successfully retrieve state variables.

To read composite or module-prefixed keys, you must have precise knowledge of the target contract's storage key names. The direct read mechanism requires exact key mapping to successfully fetch the desired state variables.

You should not use direct storage reads if contracts are on different shards or if you lack exact knowledge of the target contract's storage key names. Traditional async proxy calls remain necessary for cross-shard read operations.