mvx_sdk_js_core_skill

This skill helps developers use the MultiversX SDK core to manage accounts, endpoints, and transactions efficiently across networks.

10

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill multiversx/mx-ai-skills --skill mvx_sdk_js_core

  • SKILL.md3.5 KB

Overview

This skill provides concise guidance for using the MultiversX @multiversx/sdk-core v15 primitives: entrypoints, network providers, and transaction flows. It explains how to instantiate network clients, access low-level providers, build and send transactions, and wait for finality. The goal is to make common SDK tasks predictable and production-ready.

How this skill works

Entrypoints are network-specific clients that wrap common operations and ship with sensible default endpoints for devnet, testnet, mainnet, and localnet. Each entrypoint can create a network provider (API or proxy), controllers for transfers, and helpers to fetch nonce, send transactions, or await completion. Providers expose lower-level network methods for querying blocks, accounts, contract storage, and executing read-only contract queries.

When to use it

  • Create an entrypoint when you need a ready-made network client for devnet/testnet/mainnet/localnet.
  • Use ApiNetworkProvider for standard API requests and ProxyNetworkProvider when interacting via a gateway.
  • Call recallAccountNonce before building or signing transactions to avoid nonce conflicts.
  • Use sendTransactions to batch multiple transactions in one request.
  • Use awaitCompletedTransaction for operations that require finality (e.g., token transfers, contract state changes).

Best practices

  • Always sync account nonce from the network immediately before creating/signing a transaction.
  • Prefer awaitCompletedTransaction for critical flows to confirm finality and status.
  • Set reasonable request timeouts and retry logic for network calls to handle transient failures.
  • Batch non-dependent transfers using sendTransactions to improve throughput and reduce latency.
  • Handle and log network and RPC errors; implement exponential backoff for retries.

Example use cases

  • Initialize a DevnetEntrypoint and create an ApiNetworkProvider for integration tests.
  • Fetch account balance and nonce with getAccount before preparing a signed transfer.
  • Create a transfers controller to build a native token transfer, send it, and await completion.
  • Query contract storage or execute a VM read-only query with queryContract for UI state.
  • Batch multiple payments from a treasury account using sendTransactions for efficiency.

FAQ

Use MainnetEntrypoint for production. Configure custom URL and proxy mode only if you have a gateway or private endpoint.

When should I use ProxyNetworkProvider vs ApiNetworkProvider?

Use ApiNetworkProvider for standard API endpoints. Use ProxyNetworkProvider when you need direct gateway behavior or when your infrastructure exposes a proxy node.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
mvx_sdk_js_core skill by multiversx/mx-ai-skills | VeilStrat