multiversx-cross-contract-calls

Execute cross-contract calls in MultiversX smart contracts using the Tx Builder API.

12|5|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/multiversx/mx-ai-skills --skill multiversx-cross-contract-calls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multiversx-cross-contract-calls
Source: https://github.com/multiversx/mx-ai-skills/tree/main/skills/multiversx-cross-contract-calls
Command: npx skills add https://github.com/multiversx/mx-ai-skills --skill multiversx-cross-contract-calls

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of making cross-contract calls, handling callbacks, and managing token transfers between contracts on the MultiversX blockchain.

Core Features & Use Cases

  • Typed Proxies: Enables type-safe contract interactions, reducing errors.
  • Flexible Payment Handling: Supports EGLD and various ESDT token payment methods.
  • Synchronous & Asynchronous Calls: Facilitates both same-shard and cross-shard communication.
  • Callback Management: Provides robust mechanisms for handling asynchronous call results.
  • Use Case: When developing a DeFi application that needs to interact with a DEX for swaps and then deposit the proceeds into a lending pool, this Skill provides the exact syntax and patterns to chain these operations reliably.

Quick Start

Use the multiversx-cross-contract-calls skill to make a synchronous call to another contract using a typed proxy and send EGLD.

Frequently Asked Questions about multiversx-cross-contract-calls

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make cross-contract calls in MultiversX smart contracts?

Cross-contract calls in MultiversX smart contracts are executed using the Tx Builder API, which supports typed proxies for type-safe interactions and raw endpoint calls to communicate with other contracts.

How does asynchronous execution and callback management work for MultiversX cross-shard communication?

Asynchronous execution enables cross-shard communication using promises, requiring callback mechanisms to robustly handle asynchronous call results and manage back-transfers effectively within the contract.

What is the best way to handle EGLD and ESDT token payments in a MultiversX cross-contract call?

Handling EGLD and ESDT token payments in a MultiversX cross-contract call is managed through flexible payment handling features in the Tx Builder API, allowing reliable token transfers between contracts.

Can I use typed proxies to deploy smart contracts on MultiversX?

Typed proxies in MultiversX smart contracts enable type-safe contract interactions and can also be used for contract deployment, reducing errors and ensuring reliable execution.

Do I need a specific Rust SDK version to use the MultiversX Tx Builder API?

Using the MultiversX Tx Builder API for cross-contract calls requires Rust SDK version 0.64 or higher to access the advanced patterns for promises, callbacks, and typed proxies.

Why use typed proxies instead of raw endpoint calls for MultiversX contract interactions?

Typed proxies provide type-safe contract interactions to reduce errors, whereas raw endpoint calls offer more flexible, direct access when interacting with MultiversX smart contracts.