Changelog

Everything announced for devnet and testnet over July and August now serves mainnet.

• getAccountInfo returns an account's name and staking data without dragging balances and full NFT identifier lists along with it, and getAccountInfos reads up to 100 addresses in one call from a single state snapshot. getAccount, getAccounts and getTokenData are deprecated, with their replacements named at the call site.
• /rpc/v2 and /api/v2 serve the same methods as v1 and answer with real JSON values instead of packed strings. The v1 routes are untouched, so deployed clients keep working exactly as they do today.
• Special resolution calls are decoded by name with their arguments typed per method, including the calls they carry, and extended event data is decoded by event kind.
• getGasConfig publishes the live fee parameters and estimateTransaction prices a transaction against the current chain state, which is what makes the new gas model exactly predictable for wallets and tools.
• Many kinds of request come back faster. Owned token series are served from a maintained index, series pages are sought by key prefix, series identifiers resolve through an index, and block metadata is read without copying the block first.
• Heavy blocks are served without being assembled in memory first, because large answers are written to the connection as they are produced. Cursor pagination enforces its page size range, and the deprecated unpaginated NFT identifier lists are capped.
• RPC load metrics are exposed on a loopback endpoint for node operators.

Mainnet API reference | Mainnet Explorer

• Devnet and testnet RPC are running the latest build.
• Two new routes answer in a structured format, /rpc/v2 for JSON-RPC and /api/v2 for REST. They serve the same methods as v1, so the only change in your client is the endpoint it points at.
• Token, series, NFT, and organization property values arrive as real JSON. A property the chain stores as an array or a structure comes back as "[{\"div\":\"10000\",\"mul\":\"25\"}]" on v1 and as [{"div":"10000","mul":"25"}] on v2, so the second parse step is gone.
• Special resolution calls are decoded by name, with their arguments typed per method, including the VM migration calls they carry.
• Extended event data is decoded by event kind, covering token creation, series creation, market orders, and special resolutions.
• Numbers stay text. Chain values are big integers, and answering them as JSON numbers would lose precision.
• The v1 routes are unchanged. /rpc and /api/v1 keep returning the packed strings that deployed clients read today, so applications move when they are ready.
• Large answers are written to the connection as they are produced, for REST as well as JSON-RPC, instead of being assembled in memory first, and the memory a big answer uses is released sooner.
• Block and transaction reads repeat less work. Transaction message data is written straight into the response, block input is read without copying it first, and the gas payer is resolved once per sender instead of once per transfer.
• The published API reference now carries a v2 document next to v1.

Devnet RPC reference | Testnet RPC reference

• The testnet explorer now runs on the new Rust backend, the one devnet has been running since July.
• Token pages show the token's metadata.
• Values the chain stores as an array or a structure are displayed in that shape instead of one long packed line.
• NFT attributes are built from that same real shape, media hosted on IPFS is loaded through a gateway, long identifiers are shortened, and raw market and infusion amounts are shown scaled.
• Payloads that carry text are shown as text instead of a hex string.
• Governance calls on an event page are listed page by page.
• Event pages take shorter paths to their data. The explorer looks events up by their type directly instead of walking the whole event history, and a list now reads only the fields it displays.
• A transaction search keeps its results when a state filter is applied.
• The staking chart keeps its curve when a stake value falls outside the expected range.
• Chart colors are readable in the light theme, and the interface texts that were still fixed in English now follow the language selector.
• The mainnet explorer stays on its current backend for now.

Devnet Explorer | Testnet Explorer | explorer-backend | explorer-frontend

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

phantasma-sdk-ts | phantasma-sdk-py | phantasma-sdk | phantasma-sdk-go | PhantasmaPhoenix.RPC | PhantasmaPhoenix.NFT | phantasma-sdk-cpp | phantasma-sdk-unity

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

• The devnet explorer now runs on a new backend, rewritten from scratch in Rust and built for speed and stability.
• Every block now shows the address of the validator that produced it.
• Custom contract events appear under their real, developer-defined names (the explorer side of the custom event names release from July).
• Governance events show the decoded gas model v2 fee parameters.
• Devnet is the first deployment. The testnet and mainnet explorers stay on their current backend for now; a separate announcement will follow when they move.

Devnet Explorer | explorer-backend | explorer-frontend