- Home
- Skills
- Multiversx
- Mx Ai Skills
- Mvx Sdk Py Core
mvx_sdk_py_core_skill
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_py_core- SKILL.md3.2 KB
Overview
This skill implements core SDK operations for the MultiversX Python SDK: entrypoints, network providers, and common transaction flows. It exposes network-specific clients (Devnet, Testnet, Mainnet, Localnet), simplified APIs for sending transactions, and lower-level providers for direct node or gateway access. It’s designed to make building, broadcasting, and monitoring transactions predictable and reproducible.
How this skill works
Entrypoints are high-level clients preconfigured for common networks and provide helpers to create accounts, controllers, and network providers. Network providers (ApiNetworkProvider and ProxyNetworkProvider) expose raw calls for chain config, blocks, accounts, storage, and VM queries. Typical flow: sync an account nonce, create a transaction via a transfers controller, broadcast with entrypoint.send_transaction, and wait for finality with await_completed_transaction.
When to use it
- Building applications that interact with MultiversX networks (devnet/testnet/mainnet/localnet).
- Rapid prototyping where default network URLs and clients reduce boilerplate.
- When you need both high-level helpers (entrypoints/controllers) and low-level API access (provider queries).
- Automated testing against localnet or devnet endpoints.
- Integrating transaction lifecycle management into backend services.
Best practices
- Prefer Entrypoint classes to centralize network URL and mode configuration.
- Always recall and sync account nonce before creating or signing transactions.
- Wrap network calls in exception handling and add retries for transient failures.
- Use integer amounts (EGLD uses 18 decimals) to avoid floating point issues.
- Choose ApiNetworkProvider for standard API usage and ProxyNetworkProvider when direct gateway behavior is required.
Example use cases
- Create and fund new accounts on devnet using DevnetEntrypoint and create_account().
- Build a backend transfer service: recall_account_nonce(), create transaction via transfers controller, send_transaction(), await_completed_transaction().
- Query smart contract storage and run read-only VM queries using provider.query_contract().
- Run local integration tests against LocalnetEntrypoint with predictable URLs and no external dependencies.
- Fetch block or transaction details for analytics dashboards using ApiNetworkProvider.get_block() and get_transaction().
FAQ
Use MainnetEntrypoint with the official API URL for production workloads. Use Testnet or Devnet for testing and Localnet for isolated local development.
When should I use ProxyNetworkProvider instead of ApiNetworkProvider?
Use ProxyNetworkProvider when interacting through a gateway or when you need behavior specific to proxy endpoints; use ApiNetworkProvider for standard API queries and recommended production access.