Phantasma SDKs decode chain values into their real shapes

August 11, 2026SDK

Phantasma SDKs decode chain values into their real shapes

The latest SDK releases decode token, series, NFT, and organization properties into their real shapes, type extended event data by event kind, and type special resolution arguments per method. The Python and Rust SDKs move to a new major version.

Published latest versions, phantasma-sdk-ts 0.17.0, phantasma-sdk-py 3.0.0, phantasma-sdk 2.0.0 (Rust), phantasma-sdk-go 0.17.0, PhantasmaPhoenix.RPC 0.15.0, and PhantasmaPhoenix.NFT 0.7.13.
Structured values come from the v2 RPC routes, so point the client at /rpc/v2, or at /api/v2 for REST, to receive them.
Token, series, NFT, and organization property values decode into a value that keeps the shape the node answered, a scalar, an array, or a structure, instead of a packed string.
Extended event data is typed by event kind, covering token creation, series creation, market orders, and special resolutions.
Special resolution call arguments are typed per module and method, 43 shapes in all. A payload an SDK does not model yet is kept as it arrived rather than dropped, so a node newer than your SDK never costs you data.
Scalars stay text, because chain values are big integers and a fixed numeric type would lose precision.
Python and Rust move to a new major version because these fields change type. The TypeScript, Go, and .NET SDKs carry the same change inside their current lines.
The Unity SDK core package moves to 0.11.0 with the same typed values, and the C++ SDK received them in its source repository.

npm install phantasma-sdk-ts@latest

pip install --upgrade phantasma-sdk-py

cargo add phantasma-sdk

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

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT