Phantasma Network

Changelog

Page8 / 10
April 9, 2026TOOLING

pha-decode 0.2.0 released

The decoder now unwraps Carbon Phantasma wrappers into VM output, accepts full VM transaction hex, and falls back more cleanly when RPC only exposes script data.

  • pha-decode tx --hex now accepts three exact input shapes in one path: Carbon signed transactions, full VM transaction hex, and raw VM script hex.
  • Carbon Phantasma wrappers are now reconstructed into output.vm, so wrapped execution can be inspected without manually unpacking the envelope first.
  • Phantasma_Raw payloads now decode the inner VM transaction exactly instead of being treated as opaque bytes.
  • tx --hash still prefers carbonTxData, but now falls back to top-level RPC script data when full VM reconstruction is not possible.
  • Input detection was tightened so raw VM hex is no longer misclassified as Carbon data just because the prefix happens to look valid.

pha-decode

npm i -g pha-decode
April 8, 2026DEVNETVALIDATORS

Devnet contract attach fixed

The devnet chain update fixes token contract attach by running the attached contract constructor during registration.

  • Nexus.AttachTokenContract now uses the same registration path as fresh token-backed contract creation.
  • Attached token contracts now run their constructor during registration, so storage-backed fields such as _owner are initialized before owner checks, trigger execution, or getter calls read them.
  • This fixes attached contracts that immediately read constructor-initialized state after attach.

https://deploy-devnet.phantasma.info/

April 7, 2026MAINNETVALIDATORS

Mainnet upgraded with VM parity and contract lifecycle support

The mainnet update delivered VM parity, deterministic NFT minting, contract lifecycle, token hook, RPC, and sync reliability work in one deployment.

Important

Smart contract deployment and execution are not active yet. The code and chain updates are installed, and activation is planned for the near future.

  • The update restores Gen2 VM parity for BigInteger, VMObject, ScriptContext, storage/state interops, runtime getters, and legacy address resolution.
  • Contract lifecycle code is now installed on mainnet for custom and token-backed contracts, including deploy, upgrade, onUpgrade, and contract-owned NFT flows. Contract deployment and execution will remain unavailable until the activation step is completed.
  • Token lifecycle support was restored in the installed code for mint, burn, send, receive, infuse, and series operations. Runtime.MintTokens and Runtime.GetTokenOwner are also included.
  • NFT handling now uses deterministic Phantasma-compatible IDs and preserves imported NFT and series identities across mint, burn, transfer, and read paths.
  • Chain data repair resolutions were included for imported-state restoration: contract imports restore globals, maps/lists, token-contract indexes, missing script/ABI, and persisted imported series contract bytes.
  • Additional repair resolutions cover missing series and mint counts, imported token-contract fungible balances, imported market NFTs, and imported NFT infusions.
  • Market and token data compatibility was repaired for imported series royalties, governance-controlled early market cancellation, Token.GetBalances, and system-address transfer semantics.
  • Public RPC reads for accounts, balances, owned tokens, NFTs, and multi-result InvokeRawScript responses were corrected as part of the same mainnet rollout.
  • Fresh validator and audit-node sync were improved so nodes can recover and continue replay from partially downloaded state.
April 5, 2026SDK

Phantasma Phoenix C# and Unity SDK packages published

New Phantasma Phoenix C# packages and a refreshed Unity SDK package were published with current RPC support.

  • Published package versions now include PhantasmaPhoenix.RPC 0.5.0, PhantasmaPhoenix.NFT 0.5.0, and PhantasmaPhoenix.Protocol.Carbon 0.4.0. Developers should update to these packages for current RPC support.
  • The C# RPC wrapper was cleaned up so account, balance, token, and NFT calls match current RPC behavior more closely.
  • PhantasmaPhoenix.Protocol.Carbon now includes the deterministic Phantasma NFT mint helpers in the published package set.
  • Phantasma Phoenix Unity 0.2.0 was also published with the same RPC calling convention and tests that check the exact requests sent by the sample project.

PhantasmaPhoenix.RPC | PhantasmaPhoenix.NFT | PhantasmaPhoenix.Protocol.Carbon

dotnet package update PhantasmaPhoenix.RPC
dotnet package update PhantasmaPhoenix.NFT
dotnet package update PhantasmaPhoenix.Protocol.Carbon

Unity Package Manager

https://github.com/phantasma-io/Phantasma-UnitySDK.git?path=PhantasmaPhoenix.Unity.Core
https://github.com/phantasma-io/Phantasma-UnitySDK.git?path=PhantasmaPhoenix.Unity.LinkClient
April 4, 2026FRONTENDWALLET

Wallet connection diagnostics package published

`@phantasma/connect-react 0.1.2` was published with cleaner recovery from interrupted local wallet connections and clearer localhost diagnostics.

  • @phantasma/connect-react 0.1.2 is now published. Apps using the package should update to get the new Link connection handling.
  • The package now cancels a pending local-socket connection when the page is closed or left, which reduces stuck connection state.
  • The package now records more useful diagnostics for local wallet connection attempts, including which localhost socket hosts were tried and whether the page is running on a public site.
  • When Brave blocks localhost access from a public site, the error message now points to the likely browser permission problem instead of showing a vague transport failure.

@phantasma/connect-react

npm update --save @phantasma/connect-react