Changelog

• Devnet and testnet explorers are now running the updated explorer build.
• Transaction pages can now show a rejected transaction candidate when a searched hash was captured by RPC but is not present in the canonical block transaction list.
• The rejected-candidate view includes status, block and timestamp context, result/debug details, fee and gas data, payload/script data, and raw API/RPC responses when available.
• This makes failed submissions easier to debug on devnet and testnet without presenting them as canonical chain transactions.

Devnet Explorer | Testnet Explorer

• Published latest versions: phantasma-sdk-ts 0.8.2, phantasma-sdk-go 0.9.0, phantasma-sdk-py 2.0.3, phantasma-sdk 1.0.2, PhantasmaPhoenix.Protocol.Carbon 0.4.2, PhantasmaPhoenix.RPC 0.6.3, and PhantasmaPhoenix.NFT 0.6.3.
• phantasma-sdk-ts 0.8.2 is a large compatibility-preserving cleanup: new code can use the /public entrypoint and lowercase deep imports, while existing root and core/** imports remain available through deprecated aliases.
• TypeScript RPC calls now have an explicit result-style path for applications that want normalized HTTP and JSON-RPC errors without changing the older high-level Promise<T> methods.
• phantasma-sdk-go 0.9.0 is a breaking cleanup and hardening release under github.com/phantasma-io/phantasma-sdk-go, with context-aware RPC calls, refreshed public packages, current token and NFT builders, and shared VM serialization fixtures.
• The Python and Rust SDKs continue the newly rewritten SDK line with phantasma-sdk-py 2.0.3 and phantasma-sdk 1.0.2, adding shared Ed25519 vectors and count-aware max-gas calculation for multi-token Phantasma NFT mints.
• The latest .NET packages bring the same NFT mint gas scaling, unlimited fungible token flag handling, VMObject and ScriptContext parity fixes, and chain-aware block transaction lookup to Protocol.Carbon, RPC, and NFT.
• Across SDKs, token builders now mark unlimited fungible tokens with the big-fungible representation expected by current validator semantics.
• @phantasma/connect-react 0.1.4 was also published on the latest TypeScript SDK for applications using the shared React wallet connector.

phantasma-sdk-ts | @phantasma/connect-react | phantasma-sdk-go | phantasma-sdk-py | phantasma-sdk | PhantasmaPhoenix.Protocol.Carbon | PhantasmaPhoenix.RPC | PhantasmaPhoenix.NFT

npm update --save phantasma-sdk-ts

npm update --save @phantasma/connect-react

go get -u github.com/phantasma-io/phantasma-sdk-go

pip install --upgrade phantasma-sdk-py

cargo update -p phantasma-sdk

dotnet package update PhantasmaPhoenix.Protocol.Carbon

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

• Devnet and testnet are now running updated validator and RPC builds.
• Unlimited fungible token rows are migrated into the big-fungible storage format, keeping balance, stake, supply, and burned-counter data on the representation expected by current token semantics.
• New token semantics reject malformed small-fungible states before they can move through token creation, transfer, mint, burn, stake, or unstake paths.
• BigInteger + parsing now matches the shared VM/runtime fixtures used by the validator and SDK test suites.
• RPC token-event reconstruction now treats token repair migrations as storage representation changes, not fake token movement.
• TokenInfo updates no longer appear as fresh TokenCreate events in reconstructed RPC event data.
• Testnet also receives the validator hardening already active on devnet, including stricter VM/runtime input handling and more reliable validator status responses.

• Devnet validators are now running the latest validator build.
• Bigint handling was tightened across JSON payloads, genesis data, and signed Int256 parsing, rejecting malformed inputs more consistently.
• NFT mint and import flows now require the referenced series rows to exist, keeping token-series state stricter during contract testing.
• VM schema and sanitizer lifetime handling was hardened for contract execution paths.
• Validator status responses are protected against stalled HTTP connections, and memory usage logging is clearer for operators.

• The Python SDK documentation now includes setup, RPC, keys and addresses, VM transactions, Carbon workflows, token deployment, NFT minting, schemas and metadata, fees and broadcasting, examples, and a complete API reference.
• The Rust SDK documentation now has the same full guide structure, including read-only RPC, offline transaction examples, Carbon token and NFT workflows, and reference pages for RPC models, VM transactions, and wire-format data.
• Smart contract docs now include Storage And Data Escrow, explaining how current contract storage growth is paid through transaction-level SOUL data escrow and maxData, not by staking SOUL to a contract address.
• The SDK area was reorganized so Python and Rust sit alongside the existing C#, Unity, TypeScript, and C++ sections in the GitBook navigation.
• Existing compiler, Link Client, Unity example, and SDK pages received navigation, formatting, and wording cleanup so the developer docs read more consistently.

Python SDK docs | Rust SDK docs | Storage And Data Escrow | SDK navigation