Skip to content

Fix claim burn ownership proof validation in cucumber tests #1974

@sdbondi

Description

@sdbondi

Bounty: Fix Claim Burn Ownership Proof in Cucumber Tests

Tier: M — 60,000 XTM

Description

Two transfer cucumber tests fail at the claim burn step with "ownership proof validation failed". The integration test's burn proof construction is out of sync with the current wallet daemon validation logic, likely after recent claim burn changes in PR #1969. Update the proof construction in the test steps to match the current validation requirements.

Acceptance Criteria

  • The When I claim burn BURN_PROOF and spend it into account ... using wallet daemon ... step passes
  • "Transfer tokens to account that does not previously exist" scenario passes end-to-end
  • "Transfer tokens to existing account" scenario passes end-to-end
  • Existing claim burn scenarios in claim_burn.feature continue to pass

Context

  • Issue opened by @sdbondi
  • Error: Invalid param 'claim_proof.ownership_proof': ownership proof validation failed
  • Affected step: integration_tests/tests/steps/wallet_daemon.rs:53
  • Likely caused by PR feat(walletd): auto claim burn service #1969 changing claim burn validation logic
  • Affected scenarios in tests/features/transfer.feature

How to Claim

  1. Comment on this issue to signal intent (courtesy, not a lock)
  2. Fork the repo and do the work
  3. Submit a PR that meets the acceptance criteria
  4. First PR that passes review and gets merged wins the bounty
  5. On acceptance, XTM payment is processed

Notes

  • AI-assisted development is expected and encouraged
  • If you get stuck, ask in Discord
  • If you can't complete it within 14 days of claiming, let us know so someone else can pick it up

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions