CSPR.Cloud.Net 4.3.0

• .NETStandard 2.0

  • Microsoft.Extensions.Logging.Abstractions (>= 8.0.0)
  • Newtonsoft.Json (>= 13.0.3)

• .NETStandard 2.1

  • Microsoft.Extensions.Logging.Abstractions (>= 8.0.0)
  • Newtonsoft.Json (>= 13.0.3)

v4.3.0 — FIX (wire correctness, every item live-verified against mainnet and testnet): seven model properties bound to JSON keys the API has never emitted, so they deserialized to null (or, when non-nullable, to 0) on every row, indistinguishable from a real absent value. UndelegationData was wrong in three ways at once: DelegatorIdentifier bound delegator_identifier but the wire name is staker_identifier; EraOfCreation bound era_of_creation but it is era_id; and DelegatorIdentifierTypeId bound delegator_identifier_type_id but it is withdrawal_type_id — being a non-nullable int it read 0 on every row, silently reporting every purse withdrawal as a public-key withdrawal while its identifier was null. ValidatorPerformanceData.AverageScore bound average_score but the endpoint emits score; because that type is also ValidatorData.AveragePerformance and BidderData.AveragePerformance, every caller who requested the average_performance includer got a null score too. DEPRECATED (kept so callers still compile, to be removed in the next major): AccountData.UndelegatedBalance (the API emits undelegating_balance, already bound by UndelegatingBalance); UndelegationData.AccountInfo and CentralizedAccountInfo (that endpoint supports only the validator_account_info includer — verified by control request); ValidatorData.PendingUnstakingAmount; SwapData.Token0FtRate/Token1FtRate (never returned even when their includer is requested — the API silently ignores unknown includer names, so the includer name itself is likely wrong, pending confirmation with the CSPR.cloud team); and the four ContractResponse<T> envelope properties, whose values the API nests inside data and which ContractPackageData already binds correctly. Also: the UndelegationData test fixtures were rebuilt from captured live payloads — the previous ones invented keys the endpoint has never returned, which is why these bugs survived. No breaking changes; affected properties simply start carrying their real values. Earlier: v4.2.1 fixed x402 ValidAfter/ValidBefore wire typing; v4.2.0 added CasperCloudX402Client; v4.1.0 added CancellationToken to every REST method; v4.0.x made money values decimal.