Skip to content

sdk: strict validation and typed errors for exportReceipt output #153

Description

@karagozemin

Summary

Harden exportReceipt / serializeReceipt in packages/sdk so malformed or partial on-chain state produces a typed error rather than an incomplete receipt.

Motivation

Receipts are the verifiable artifact users rely on. Silently emitting an incomplete receipt undermines the 'protocol owns fairness' guarantee.

Acceptance criteria

  • Missing/invalid fields raise a dedicated error class.
  • Receipt schema version is always present and validated.
  • Round-trip test (serializeReceiptparseReceiptverifyReceipt).
  • Tests for at least three malformed-input cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26area: sdkTypeScript SDKcomplexity: mediumExpected medium implementation complexityenhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions