Changelog

• Devnet and testnet validators are now running the latest VM context fix.
• The rollout fixes Runtime.PreviousContext handling across same-contract helper frames, cross-contract calls, deep nested calls, constructors, upgrade triggers, and failed contract switches.
• Fresh VM executions now receive the explicit previous context that belongs to the runtime call, and nested contract switches restore that value after successful returns or faults.
• Contracts that inspect Runtime.Context and Runtime.PreviousContext should now see stable caller identity through nested contract flows.
• The validator update includes parity coverage for root calls, self-switch calls, multi-contract nested calls, constructors, upgrade triggers, and failed switches.

• Mainnet is now running updated validator and RPC builds.
• Token semantics V3 is active on mainnet. Staking organization membership now stays aligned when a clean unstake drops an address below the configured threshold.
• Token metadata validation now rejects small-fungible staking organization thresholds that require the big-integer representation, preventing new malformed small-fungible staking metadata from being admitted.
• The SOUL masters organization repair has been applied: 74 stale below-threshold members were removed, and 13 requalified member timestamps were rewritten from the audited repair payload.
• Post-deployment verification for the SOUL masters repair reported a clean public row check and a clean watcher scan, with no remaining missing eligible members or bad stake values in the audited range.
• stake.GetUnclaimed now reads claimable KCAL without mutating stake state, so reward previews and read-only checks do not alter validator-side staking rows.
• RPC now exposes organization reads through getOrganization, getOrganizations, getOrganizationMembers, and getOrganizationMember, with organization-name queries and cursor pagination for member lists.
• Cached JSON-RPC responses now preserve embedded result objects correctly when the response is served from cache.

Token semantics V3 transaction | SOUL masters repair transaction

• 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