Changelog

• Devnet and testnet RPC are running the latest build.
• A new getAccountInfo returns just the account name and staking information for an address. It is the lightweight replacement for getAccount, which packed balances and full NFT identifier lists into the same response.
• A new getAccountInfos returns that same record for a batch of up to 100 addresses in one call, read from a single state snapshot and returned in request order — one round trip instead of one per address.
• getAccount and getAccounts are now deprecated. Use getAccountInfo for name and staking data, together with the cursor-paginated getAccountFungibleTokens and getAccountNFTs for balances and NFTs.
• getTokenData is deprecated in favor of getNFT, which returns the same result and additionally supports the extended flag.
• NFT and series reads take shorter paths: owned token series are served from a maintained owner index, series pages are sought by key prefix instead of being filtered after the fact, and series identifiers resolve through an index instead of a scan.
• Pagination is bounded. Cursor-paginated endpoints enforce the accepted pageSize range, and the deprecated unpaginated NFT identifier lists are capped at 10,000 entries per token while the true count is still reported.
• The published API reference now carries a description and a deprecation marker for each endpoint, so the replacement for a deprecated call is visible directly in the documentation.
• Node operators can read RPC load metrics from a loopback Prometheus endpoint.

Devnet RPC reference | Testnet RPC reference

• Published latest versions: phantasma-sdk-ts 0.16.0, phantasma-sdk-py 2.7.0, phantasma-sdk 1.7.0 (Rust), phantasma-sdk-go 0.16.0, PhantasmaPhoenix.RPC 0.13.0, and PhantasmaPhoenix.NFT 0.7.10.
• Every SDK adds a client for getAccountInfo, which reads an account's name and staking information without pulling balances or full NFT identifier lists along with them.
• Every SDK also adds a client for getAccountInfos, so an application can read up to 100 accounts in a single call instead of one call per address.
• getAccount, getAccounts, and getTokenData are marked deprecated in the SDKs, with the replacement named at the call site, so the compiler or editor points to it while you migrate.
• Cursor-paginated methods now document the accepted pageSize range that the nodes enforce.
• The Unity SDK adds getGasConfig and estimateTransaction clients and moves its core package to 0.10.0, bringing it in line with the gas model v2 fee estimation already available in the other SDKs.
• The C++ SDK received the same additions 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 update --save phantasma-sdk-ts

pip install --upgrade phantasma-sdk-py

cargo update -p phantasma-sdk

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

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

• Devnet is running the latest validator and RPC builds, and gas model v2 is now active on devnet, switched on through a governance special resolution.
• Gas model v2 is a redesigned fee model. A transaction's fee is based on the real work it performs — its computation and the data it moves — together with the real, lasting cost of the state it keeps on-chain.
• This is the economic foundation for Phantasma's upcoming sidechains: gas model v2 makes fee policy configurable per chain, introduces a block producer reward share, and lays the groundwork for fee sponsorship — the building blocks a multi-chain network needs.
• The refundable SOUL storage deposit is preserved: applications that store data get their deposit back when that data is removed.
• Exact fee estimation arrives with the model. A new getGasConfig RPC method exposes the live fee parameters, and a new transaction estimation endpoint lets wallets and tools compute exact fees before sending. The Phantasma SDKs ship matching fee calculators in the same release.
• Activation is atomic and governed: the new model turns on in a single, producer-approved resolution, and the full transaction history stays reproducible under the previous rules.
• Gas model v2 is being trialed on devnet first. Mainnet continues on the current model while devnet proves out the new one; a dedicated announcement will follow when it is scheduled for mainnet.

• Published latest versions: phantasma-sdk-ts 0.14.0, phantasma-sdk-py 2.5.0, phantasma-sdk 1.5.0 (Rust), phantasma-sdk-go 0.14.0, PhantasmaPhoenix.Protocol.Carbon 0.5.0, PhantasmaPhoenix.RPC 0.11.0, and PhantasmaPhoenix.NFT 0.7.8.
• Every SDK now reads the live gas configuration and includes a Tier-1 fee estimator that computes exact fees for native operations before a transaction is sent.
• Each SDK adds a client for the new transaction estimation endpoint, so wallets and tools can request an exact fee estimate for a prepared transaction.
• Block responses now expose the block producer address across the SDKs.
• The C++ SDK received the same additions in its source repository.

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

npm update --save phantasma-sdk-ts

pip install --upgrade phantasma-sdk-py

cargo update -p phantasma-sdk

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

dotnet package update PhantasmaPhoenix.Protocol.Carbon

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

• Custom events emitted by smart contracts now keep their real, developer-defined names end-to-end.
• Devnet and testnet validators emit these events in a consistent named form, and RPC reconstructs older custom events into the same form, so integrators get stable, meaningful event names instead of a generic placeholder.
• The TOMB smart contract compiler emits custom events in the same named form as of pha-tomb 2.2.0.

pha-tomb

dotnet tool update --global pha-tomb