Changelog

• 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

• Mainnet is now running updated validator and RPC builds.
• May 2026 inflation and Soul Master rewards have been applied on mainnet.
• This release brings a broad round of security hardening and adds another layer of defense-in-depth across the validator and RPC.
• The VM enforces robust execution guardrails, with firm limits on call depth, nesting, structure size, and large intermediate values, so contract execution stays predictable and safe.
• Input validation was reinforced across the serialization and decoding paths, so nodes confidently handle even malformed or oversized data.
• Network-layer protections were strengthened with tighter connection and message-size limits, keeping nodes stable under heavy network load.
• Block and transaction size limits were tightened to keep block production lean and predictable.
• Consensus failover and leader recovery are faster and more reliable.
• The validator status endpoint is faster and more resilient, served from a cached snapshot, protected against slow connections, and with more headroom for operators.
• VM opcode handling was refined and now ships with broader test coverage.
• RPC added connection limits and request rate limiting to keep public mainnet endpoints fast and responsive under load, and event reconstruction no longer emits a duplicated NFT mint event.
• These same validator and RPC builds are now also running on testnet, without the inflation resolution.

May 2026 inflation transaction | Soul Master rewards transaction

• Devnet validators and RPC are now running newer builds focused on reliability and input hardening.
• These builds strengthen resilience across VM execution, serialization, and the network layer, and add RPC connection limits and request rate limiting for steady performance under load.
• RPC event reconstruction no longer emits a duplicated NFT mint event.

• Mainnet is now running updated validator and RPC builds.
• The VM Runtime.PreviousContext fix is now live on mainnet. Contracts that read Runtime.Context and Runtime.PreviousContext see stable caller identity through same-contract helper frames, cross-contract calls, deep nested calls, constructors, upgrade triggers, and failed contract switches.
• Validators now log special-resolution failures as errors, making operational issues easier to spot.
• RPC no longer crashes when event reconstruction encounters an invalid address; these cases are now handled cleanly and are covered by new regression tests.