Changelog

• Mainnet is now running updated RPC and validator builds.
• RPC now handles expected client-side failures more cleanly: missing token lookups, invalid null JSON-RPC parameters, aborted requests, disconnected clients, and block-hash transaction-count misses no longer escalate into noisy server-style errors.
• RPC event decoding was also refreshed so nested Token calls and special-resolution activity are reconstructed more reliably for mainnet consumers.
• The mainnet resolution set in this rollout also burned the 700,000 SOUL that Sergio minted during his last attack on the chain in January 2024.
• Validator networking is more stable under failed ION reconnect cycles, and validator logs now make peer connection failures easier to diagnose.

Future VM fixes are also installed in the validator build for later smart contract activation.

• Runtime.MintToken same-token context handling was corrected for future contract-driven NFT mint flows.
• Duplicated-series Runtime.MintToken mints now derive stable NFT ids more reliably.
• Smart contract deployment and execution are still inactive on mainnet for now.

• Expected client errors and normal compatibility misses no longer fill RPC warning logs.
• getToken, getTokenSeries, and getTokenSeriesById now return a clean client error when the token symbol does not exist.
• JSON-RPC now returns Invalid params when null is passed into a required parameter.
• If the client disconnects or cancels the request, RPC now stops that request more cleanly without fatal write errors.
• GetBlockTransactionCountByHash now keeps the usual unknown-block response instead of turning that case into a server error.

• Devnet validators now back off failed ION reconnect attempts instead of repeatedly retrying unhealthy peers, and failed or mismatched handshakes are cleaned up more safely.
• Validator logs now report outbound ION connection failures with peer, target, endpoint, and socket error details, making producer connectivity issues easier to diagnose.
• RPC now shuts down ION producer connections more safely when failed connects or background read/write tasks are still unwinding.
• RPC now reconstructs Token module events more accurately from nested Token calls and governance SpecialResolution payloads, including transfer, burn, mint, and market-related paths.
• Smart-contract NFT minting on devnet includes same-token Runtime.MintToken context fixes, preserving the user witness while adding the token contract witness when a token contract mints its own NFTs.
• Duplicated-series Runtime.MintToken mints now derive stable Phantasma NFT ids from the series id and mint number, including empty-ROM follow-up mints.
• Token creation, deploy, attach, and upgrade lifecycle events now use Gen2-compatible string payloads, so event consumers can read token and contract names consistently.
• Validators also include special-resolution liveness recovery: if a leader stops proposing a pending special resolution while producers are caught up, producers can trigger a soft reelection without interrupting normal peer traffic.

• PhantasmaPhoenix.Protocol.Carbon 0.4.1, PhantasmaPhoenix.RPC 0.6.1, and PhantasmaPhoenix.NFT 0.6.1 are now available on NuGet.
• Protocol.Carbon adds typed token contract call arguments for token series, fungible mint and burn, non-fungible transfer and burn, and metadata update calls.

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

dotnet package update PhantasmaPhoenix.Protocol.Carbon

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

• pha-decode 0.3.0 is now published on npm; update the global CLI before using the new address tools.
• pha-decode address can now derive Phantasma addresses from WIF, 32-byte private keys, modern BIP39 seed phrases, and legacy Poltergeist seed phrases.
• Modern seed phrase derivation supports an explicit --index; legacy Poltergeist seed phrases support --legacy-password for old wallet recovery flows.
• Private inputs are redacted from CLI output, and --stdin lets scripts pass WIF, private key, or seed phrase values without putting them directly in command arguments.

pha-decode

npm update -g pha-decode