Changelog

• Devnet and testnet RPC now support API keys that grant higher rate-limit tiers: node operators can issue keys for higher-volume access, and can optionally run a node in keys-only mode.
• All seven Phantasma SDKs can now attach an API key to the RPC client, so requests use the matching rate-limit tier on nodes that issue keys.
• The same RPC build returns NFT lookups that find nothing as a clean not-found result instead of surfacing as an error.
• Controlled API errors now propagate with their intended status and message instead of being flattened by a catch-all handler.
• Updated SDK packages: phantasma-sdk-ts 0.11.0 (TypeScript), phantasma-sdk-py 2.2.0 (Python), phantasma-sdk 1.2.0 (Rust), phantasma-sdk-go v0.11.0 (Go), and PhantasmaPhoenix.RPC 0.8.0 (.NET), plus updated C++ and Unity SDKs.

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

TypeScript | Python | Rust | Go | .NET | C++ | Unity

• Phantasma Link v5, the new dApp-to-wallet connection protocol, is now stable (specification v1.0), and the v5 client is available in the TypeScript SDK (phantasma-sdk-ts 0.10.1).
• One structured message envelope (a JSON-RPC 2.0 profile) replaces the old string protocol and works across every transport, so requests are typed, independent, and can run concurrently.
• A capability handshake lets the dApp and wallet agree up front on supported methods, chains, transaction formats, payload sizes, and features, instead of guessing from a version number.
• Every session is end-to-end encrypted with NaCl and is a real, revocable session; relays only ever see ciphertext.
• The same envelope runs over several transports: the Ecto browser extension, a desktop loopback channel (now bound to localhost only), a mobile deeplink path, and a self-hosted relay for large payloads and cross-device pairing.
• Mobile and iOS are first-class: the deeplink path needs no wallet-hosted local server and keeps working even when the relay is down.
• The old ~32 KB request limit is gone. Transactions can now carry up to the chain's real ceiling of 1 MiB of metadata and 32 MiB per transaction.
• Existing v1–v4 dApps keep working. Phantasma Link v5 is purely the connection layer and changes nothing on the chain, validators, or RPC.

npm update --save phantasma-sdk-ts

Phantasma Link v5 specification | phantasma-sdk-ts on npm

• React bindings for Phantasma Link v5 are published as phantasma-link-react (renamed from @phantasma/connect-react). Wrap your app once, drop in a connect button, and call the typed pha_* methods through a small reactive store over the v5 client.
• A public relay is live at link.phantasma.info. It is an end-to-end-blind WebSocket pub/sub server that carries large transactions, cross-device sessions, and wallet events while never seeing their content.
• A playground is live at link-test.phantasma.info. It runs the same operations side by side over Phantasma Link v5 and the legacy v4, so you can compare them and try the cross-device relay (QR) and same-device deeplink flows.

npm install phantasma-link-react

phantasma-link-react on npm | Relay | Playground

• Devnet and testnet RPC are now running a newer build focused on reliability.
• Token-event and transaction reconstruction handles edge and null values more robustly, so responses stay clean even on unusual inputs.
• Legacy storage structures are default-initialized, removing a class of latent null-handling defects.
• The build now ships under a stricter zero-warning policy for cleaner, more maintainable releases.

• A Phantasma Link v5 client is now available for C# as PhantasmaPhoenix.Link 0.2.0, with ECDH pairing, the relay and deeplink transports, sessions with revoke, sign operations, and the script transaction format.
• PhantasmaPhoenix.Protocol.Carbon 0.4.4, PhantasmaPhoenix.RPC 0.7.4, and PhantasmaPhoenix.NFT 0.7.4 were published, with optional RPC response-model fields made nullable for safer deserialization and license alignment with the TypeScript SDK.

dotnet package add PhantasmaPhoenix.Link

dotnet package update PhantasmaPhoenix.Protocol.Carbon

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

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