Changelog

• RPC now recovers stale ION producer connections more safely, including a fix for connections that start closing while background send/read work is still unwinding.
• JSON-RPC response id values are preserved from incoming requests, including integer ids, string ids, null ids, and omitted ids.
• Expected empty-result reads and explicit client bad requests are separated from real RPC failures in logs, reducing error noise from normal account, block, token, NFT, transaction, and cache-miss paths.
• GetBlockByHash now returns HTTP 200 for a valid lookup that has no matching block instead of treating that miss as an API error.
• Mainnet validators now include special-resolution starvation leader reelection, allowing producers to request a soft reelection when a leader stops proposing the pending special resolution while the network remains otherwise connected.
• Validator operations logs are easier to read and correlate: Raft and network logs include peer nicknames, successful leader election is highlighted, file logs strip console color codes, ordinary log output is flushed periodically, and log lines use UTC timestamps.

Future contract groundwork is also included in the installed validator code, but smart contract deployment and execution remain inactive on mainnet for now.

• Configurable smart contract runtime logging is installed for later contract debugging, including VM trace output, halt failures, rejections, assertions, and unexpected exceptions.
• Runtime.MintToken now handles schema-backed NFT ROM and RAM payloads used by future smart contract mint flows.
• Token creation, contract deploy, and contract upgrade events now encode the affected symbol or contract name in the event payload for the future contract lifecycle path.

• Devnet validators are running the latest chain build with the NFT minting fixes needed for the next round of smart contract testing.
• Runtime.MintToken now accepts serialized VM struct payloads for schema-backed NFT ROM and stores them using the token's persisted ROM schema.
• Schema-backed NFT RAM now follows the same path, so smart contracts can persist typed RAM payloads through the normal NFT mint flow.
• This enables Saturn v4 DEX work to begin on devnet, including contract flows that mint pool ownership certificate NFTs.

• Smart contract runtime logs are now written into validator logs with transaction context, covering contract trace output, script halt failures, VM errors, rejections, assertions, and unexpected exceptions.
• Validator file logs now remove terminal ANSI color sequences while keeping readable message text, so log files are no longer polluted with console color codes.
• Validator log lines now use UTC timestamps, making cross-host incident review and RPC/chain correlation easier.
• The devnet RPC now preserves JSON-RPC response id values from incoming requests, including integer ids, string ids, and null or omitted ids.
• RPC ION producer connections now detect stale producer sessions after unanswered outbound work and recover them instead of continuing to select a dead connection.

• PhantasmaPhoenix.RPC 0.6.0 and PhantasmaPhoenix.NFT 0.6.0 are now available on NuGet. Developers using either package should update to the current versions.
• JSON-RPC request and response ids now support the protocol-valid forms: integer ids, string ids, null ids, and omitted ids.
• RPC responses now serialize the exact id value supplied by the caller instead of relying on an implicit default response id.
• Invalid JSON-RPC id shapes such as objects, arrays, and floating-point values are rejected during deserialization.
• PhantasmaPhoenix.NFT 0.6.0 now depends on PhantasmaPhoenix.RPC 0.6.0, so NFT integrations use the same corrected RPC id handling.

PhantasmaPhoenix.RPC | PhantasmaPhoenix.NFT

dotnet package update PhantasmaPhoenix.RPC

dotnet package update PhantasmaPhoenix.NFT

• LMDB read scopes are now kept short around the local database read and are no longer held across awaited network calls.
• The stability fix covers account NFT reads, single NFT reads, NFT batch reads, token NFT pagination, and transaction lookup with recent-transaction fallback.
• Extended token responses now temporarily tolerate the historical GFLP tokenSchemas row with trailing bytes, so clients can still receive schema data while the historical row remains in storage.
• No client API change is required for this update.