Property-based test parity for EVM, Solana, and CKB

[truthixify]

Tier: M (2-4 days) | Type: test

Context. test/chains/stellar/properties.test.ts covers scalar arithmetic and derivation invariants for Stellar (PR #46) but the other three chains rely on hand-rolled fixture tests. A regression in the scan.ts or keys.ts of EVM / Solana / CKB won't be caught by the same class of property, and the differential harness only exists for Stellar.

Scope.

• Mirror the Stellar property suite for evm, solana, ckb: key-derivation determinism, meta-address round-trips, scan inclusion invariant, view-tag false-negative rate.
• Reuse fast-check conventions (FC_RUNS env, seeded runs).
• Wire each into pnpm test:fuzz matrix.
• Time-budget: each suite completes under 60s at default FC_RUNS.

Acceptance.

• test/chains/{evm,solana,ckb}/properties.test.ts exist and pass
• FC_RUNS=100000 completes under 5 min per chain locally
• Same invariants tested across all four chains (checklist in each file header)
• Added to the nightly fuzz CI job

Files. test/chains/evm/properties.test.ts (new), test/chains/solana/properties.test.ts (new), test/chains/ckb/properties.test.ts (new), .github/workflows/ci.yml.

[Sajjadd-dev]

@Sajjadd-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I’m interested in working on this issue. I have experience with similar tasks and can begin immediately.

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

[elijah4196]

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

Hi,
I'd like to be assigned to this issue.
I've reviewed the requirements and I'm confident in my ability to solve this issue.
I'll ensure the solution is maintainable, thoroughly tested, and fully aligned with the project's standards and acceptance criteria.

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

[collinsezedike]

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

I've worked with fast-check property tests before, and porting an existing invariant suite to new chains is worth doing carefully since a subtly different invariant per chain defeats the whole point of parity testing.

Here's my plan:

• Read test/chains/stellar/properties.test.ts closely to extract the exact four invariants: key-derivation determinism, meta-address round-trips, scan inclusion, and view-tag false-negative rate, along with how each is expressed as a fast-check property
• Port each invariant to evm, solana, and ckb, adapting only the chain-specific key/address generation and scan.ts/keys.ts calls, while keeping the actual property assertions structurally identical across all four chains
• Reuse the existing FC_RUNS env var convention and seeded-run setup rather than inventing new test infrastructure
• Add a checklist comment in each file's header confirming the same four invariants are covered, matching Stellar's suite
• Wire all three new suites into pnpm test:fuzz and the nightly fuzz CI job in .github/workflows/ci.yml
• Verify each suite completes under 60s at default FC_RUNS and under 5 minutes at FC_RUNS=100000, tuning generator complexity if any chain's suite runs meaningfully slower than Stellar's

Happy to start as soon as I'm assigned.

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

[nurudeenheroic]

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

Hello maintainer, I would like to fix this issue, please assign this to me

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

[MrOmale]

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

Hi Maintainer, I’d be happy to work on this issue. I have experience with similar implementations and can ensure the work is completed efficiently and to a high standard.

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

[pharwasz]

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

Hi, I would like to work on this issue

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

[drips-wave]

Congratulations, @elijah4196! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @elijah4196: 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 🌊