mvx_sdk_js_tokens_skill

This skill simplifies building and managing MultiversX token transfers, issuance, and queries in JavaScript/TypeScript SDKs for faster safe deployments.

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_tokens

  • SKILL.md3.2 KB

Overview

This skill provides token operations for the MultiversX TypeScript/JavaScript SDK, covering ESDT (fungible), NFT and SFT workflows. It explains how to create transfers, issue tokens, set roles, and query token state using SDK controllers and the network provider. The content highlights concrete code patterns, required parameters, and common pitfalls to avoid.

How this skill works

The SDK exposes controllers for transfers and token management plus a network provider for queries. You create transactions (native EGLD, ESDT, NFT/SFT) via controller helper methods, sign/send them, and optionally await completion to obtain outcomes like token identifiers. Role management and token issuance require specific flags and sufficient gas; queries return token lists or single token objects for accounts.

When to use it

  • Send native EGLD payments between accounts
  • Transfer fungible ESDT tokens or batched token transfers
  • Transfer or mint NFTs and SFTs (non-fungible / semi-fungible assets)
  • Issue new fungible tokens or register NFTs/SFTs on-chain
  • Set or update special roles (mint/burn/creator permissions)
  • Query account tokens and NFT collections for UI or reconciliation

Best practices

  • Remember EGLD uses 18 decimals; custom tokens set numDecimals at issuance
  • Use token identifiers in the form TICKER-hexhash (e.g., USDC-a1b2c3) when referencing tokens
  • Start NFT nonces at 1 and increment per mint to avoid collisions
  • Provision sufficient gas for token operations (expect ~60,000,000+ gas for many actions)
  • Await transaction completion when you need on-chain outcomes like a new token identifier
  • Set explicit role flags during issuance or via role management transactions to limit privileges

Example use cases

  • Create a payment widget that sends native EGLD or ESDT tokens from users to a merchant account
  • Issue a new utility token (fungible) with custom decimals and supply, then distribute initial balances
  • Mint an NFT collection and set creator/mint roles so a dApp can mint items programmatically
  • Transfer an SFT batch to represent in-game consumables with quantity >1
  • Build a dashboard that queries and displays all fungible tokens and NFTs owned by a user

FAQ

Send the issuance transaction and await the controller’s completion helper; the outcome contains the tokenIdentifier returned on-chain.

What decimals should I use for custom tokens?

Choose decimals based on smallest unit you need; common choices are 6 or 18. Remember EGLD is 18 decimals and client UIs must format amounts accordingly.

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