Changelog

• 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 Phantasma RPC support.
• The C# RPC wrapper was cleaned up so account, balance, token, and NFT calls match current Phantasma 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

• @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

• Devnet was reset to a testnet snapshot for the next round of chain and contract testing.
• Token semantics versioning was added so new token lifecycle behavior can be enabled cleanly without changing historical replay rules.
• VM and token replay were hardened: unsigned block #0 CreateToken replay was restored, malformed token metadata and royalty sources are rejected, and wide BigInteger guard forms are clamped to the expected 256-bit payload.
• State reads are stricter for token, governance, VM, market, organization, persisted series metadata, and Raft storage data.
• Validator and node stability fixes include safer rollback after app-state write failures, a corrected Raft vote freshness comparison, safer /dev/log iteration, signal-safe shutdown, and a guard against HTTP shutdown crashes after failed initialization.

• The VM documentation was expanded with clearer coverage for architecture, interop, opcodes, and runtime types.
• The TypeScript SDK docs were refreshed for connect-react, wallet connection options, EasyConnect, and PhantasmaLink.
• pha-deploy documentation was substantially rewritten to match the current compile, deploy, upgrade, and attach commands.
• Compiler docs and examples were updated for the current deployment workflow.

pha-deploy | React wallet connection | Token Deployment UI | Unity installation

• A dedicated contract tab was added for custom contract deploy and upgrade, plus token attach and token contract upgrade.
• The UI accepts compiled .pvm and .abi artifacts directly and applies separate gas defaults per lifecycle action.
• Token attach and token contract upgrade use the token selected in the side panel as the target token.
• The frontend was also updated to phantasma-sdk-ts 0.7.0 to match the newer Link signing support.

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

Token Deployment UI | pha-deploy contract lifecycle commands