Changelog

• Devnet and testnet are now running updated validator and RPC builds.
• Validator status responses now expose optional block heights and recent block samples for dashboard health cards.
• Token Notify events for token operations are fixed on both networks.
• The claimable KCAL / staking booster reward calculation fix is active on devnet and testnet, with RPC aligned to the validator calculation.
• Historical replay compatibility fixes are also active in the deployed validator build.

• Devnet and testnet are now running the updated validator build.
• The token repair resolution has been deployed. It restores missing token-backed contract metadata, token flags, script/ABI data, and contract registry rows so repaired tokens can be resolved and executed consistently.
• Testnet now executes Phantasma smart contracts, giving developers a public test network for contract transactions before mainnet activation.
• The validator VM now supports Runtime.WriteToken RAM writes, including the onWrite trigger path used by NFT contracts that update token RAM.
• Smart contract execution also keeps anonymous witness context across block production, blocks public Initialize re-entry, and preserves duplicated-series Runtime.MintToken behavior for follow-up NFT mints.
• NFT owner lookups and organization member lookups now use exact key ranges, fixing cases where stored little-endian ids could make valid entries disappear from reads.
• Validator reliability was tightened as well: the inflation scheduler now backs off failed paid inflation transactions instead of producing repeated empty blocks, and Raft voting now rejects stale candidates more strictly.
• pha-tomb 2.1.1 is available on NuGet with Runtime.WriteToken marked as available in native-method checks, so compiler diagnostics match the validator build now deployed to devnet and testnet.

pha-tomb

dotnet tool update --global pha-tomb

• Mainnet is now running updated Phantasma RPC and validator builds.
• Phantasma 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, Phantasma 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.
• Phantasma RPC now shuts down ION producer connections more safely when failed connects or background read/write tasks are still unwinding.
• Phantasma 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.