`@wraith-protocol/test-vectors` published package

[truthixify]

Tier: L (1-2 weeks) Type: feature

Context

Other-language reimplementations of the stealth math (Go indexers, Rust agents, Swift mobile) need a shared corpus to verify their crypto matches the reference TS SDK. Ship as a separate npm package.

Scope

• New packages/test-vectors/ workspace package
• 5 JSON vector files per chain (key derivation, stealth gen, scan match, signing, encoding) with ≥ 100 vectors each
• Generation script that produces vectors deterministically from a seed
• checksum.json with SHA-256 of each file
• README with cross-language consumption examples (Rust / Go / Python)
• Published to npm at v1.0.0

Acceptance criteria

• Package published
• SDK tests updated to consume the vectors
• Cross-language README
• Tagged v1.0.0

Files to start with

• New: packages/test-vectors/
• pnpm-workspace.yaml

[maztah1]

@maztah1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can i work on this issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @maztah1 to this issue.

[drips-wave]

Congratulations, @maztah1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @maztah1: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[truthixify]

@maztah1 Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.