Changelog

• Published latest versions: phantasma-sdk-ts 0.9.2, phantasma-sdk-go 0.10.2, phantasma-sdk-py 2.1.2, phantasma-sdk 1.1.3, PhantasmaPhoenix.Protocol.Carbon 0.4.3, PhantasmaPhoenix.RPC 0.7.3, and PhantasmaPhoenix.NFT 0.7.3.
• SDKs now include organization RPC models and helper calls for getOrganization, getOrganizations, getOrganizationMembers, and getOrganizationMember, matching the current name-first RPC API.
• Organization member and organization list reads use cursor-aware result models, so applications can inspect groups such as masters through the public organization API.
• JSON-RPC clients and response models have stricter id and envelope validation. Mismatched or malformed response ids are rejected, while valid numeric and string ids from RPC nodes remain supported.
• Carbon serialization readers have stronger length checks for array-style payloads, reducing the chance that malformed Carbon data is accepted or decoded with the wrong bounds.

phantasma-sdk-ts | phantasma-sdk-go | phantasma-sdk-py | phantasma-sdk | PhantasmaPhoenix.Protocol.Carbon | PhantasmaPhoenix.RPC | PhantasmaPhoenix.NFT

npm update --save phantasma-sdk-ts

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

• Smart contract deployment and execution are now active on Phantasma mainnet.
• Developers can deploy and upgrade custom Phantasma VM contracts through Runtime.DeployContract and Runtime.UpgradeContract, including constructor execution, onUpgrade, and ABI-aware upgrade handling.
• Token-backed contracts are active on mainnet. Nexus.CreateToken can create token contracts with script and ABI data, and Nexus.AttachTokenContract can attach VM logic to eligible existing tokens.
• Token lifecycle hooks are active for contract flows, including mint, burn, send, receive, infuse, series creation, and RAM write behavior.
• The NFT contract stack is available on mainnet: deterministic Phantasma NFT ids, series-aware minting, schema-backed ROM and RAM payloads, Runtime.MintToken, Runtime.WriteToken, onWrite, Runtime.ReadToken, Runtime.ReadTokenROM, Runtime.ReadInfusions, and Runtime.GetOwnershipsBySeries.
• Contract-side fungible token support is available for eligible custom tokens through Runtime.MintTokens, with Runtime.GetTokenOwner available for token ownership reads.
• The restored VM runtime includes the compatibility work needed by existing Phantasma contract patterns: BigInteger, VMObject, ScriptContext, contract storage, Data.*, Map.*, List.*, runtime getters, contract address resolution, and multi-result script execution.
• Mainnet token-backed contract state needed by the VM has been repaired, including token metadata, token flags, ABI rows, and contract registry rows.
• Validator runtime logging and lifecycle event payloads now make contract deploy, upgrade, and token creation activity easier to track.
• RPC event reconstruction has been updated for nested Token calls, token repair migrations, Token Notify events, and contract lifecycle activity. RPC access to smart contract reads and writes remains controlled by each RPC node's operator configuration.
• TOMB compiler support, pha-deploy contract lifecycle commands, and the token deployment UI have been updated around the launch.
• Current SDK releases for TypeScript, Go, Python, Rust, and .NET support the mainnet contract path with current VM transaction builders, token and NFT flows, gas handling, and RPC behavior.
• Developer documentation now covers the current smart contract stack, including SDK guides, VM transaction flows, token and NFT workflows, and storage/data escrow guidance.
• Result: developers can build against the restored Phantasma VM lifecycle on mainnet: deploy contracts, attach token logic, create NFT series, mint and update NFTs with contract-controlled metadata, and integrate those flows through current RPC and SDK packages.

Mainnet VM config | Token Deployment UI | pha-deploy docs | Storage And Data Escrow

• pha-decode 0.3.2 and pha-deploy 0.5.1 are now published on npm as separate Phantasma CLI tooling packages.
• pha-decode can now decode payload-only RPC carbonTxData by passing the matching --carbon-tx-type.
• pha-decode tx --rpc-json tx.json and pha-decode tx --rpc-json - accept a raw getTransaction result object or a JSON-RPC response, so copied RPC output can be decoded without manually rebuilding a full transaction hex string.
• Direct carbonTxData decoding can include optional RPC context such as payload, expiration, gas payer, gas limit, and signature count when that data is available.
• Transaction input validation is stricter: the CLI rejects mixed transaction input modes and requires an explicit Carbon transaction type for payload-only data.
• pha-deploy 0.5.1 refreshes the CLI runtime and dependency baseline for Node.js 22 while preserving the existing contract compile, deploy, upgrade, and attach workflow.

pha-decode | pha-deploy | pha-decode source | pha-deploy source

npm update -g pha-decode

npm update -g pha-deploy

• 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