Cross-chain conformance test suite

[truthixify]

Labels: Stellar Wave, test, interop, stellar, drips, help-wanted
Tier: L (1–2 weeks)
Type: test

Context

Each chain module in the SDK implements deriveStealthKeys, generateStealthAddress, scanAnnouncements, etc. — the same conceptual operations, adapted to each chain's curve and hashing. The tests for each chain live in isolation. There's nothing that verifies all four chains satisfy the same behavioral contract.

We want a parameterized test suite that runs every chain through the same scenarios.

Scope

Create test/conformance/ with a single test file that imports a chain module by name and runs a battery of operations:

The contract every chain must satisfy

// pseudo-code
for chain of ['evm', 'stellar', 'solana', 'ckb']:
  const m = chainModule(chain)

  test('round-trip: derive → encode → decode → match'):
    keys = m.deriveStealthKeys(TEST_SIGNATURE)
    metaAddress = m.encodeStealthMetaAddress(keys.spendingPubKey, keys.viewingPubKey)
    decoded = m.decodeStealthMetaAddress(metaAddress)
    assert decoded.spendingPubKey === keys.spendingPubKey
    assert decoded.viewingPubKey === keys.viewingPubKey

  test('stealth payment scan correctness'):
    generated = m.generateStealthAddress(keys.spendingPubKey, keys.viewingPubKey)
    announcement = mockAnnouncement(generated)
    matches = m.scanAnnouncements([announcement], keys.viewingKey, keys.spendingPubKey, keys.spendingKey)
    assert matches.length === 1
    assert matches[0].stealthAddress === generated.stealthAddress

  test('stealth private key spends'):
    p_stealth = m.deriveStealthPrivateKey(keys.spendingKey, generated.ephemeralPubKey, keys.viewingKey)
    pub = pointMul(p_stealth, G)
    assert pub === generated.stealthPubKey

  test('view-tag false-positive rate'):
    // 1000 random announcements not destined for us
    // assert ~ 1000/256 ≈ 4 pass the view-tag filter

Why parameterize

When a new chain (Hedera? Aptos?) is added, plugging it into the conformance harness immediately tells us if the implementation matches the protocol-level invariants. Right now we have no such safety net.

Things to avoid

• Don't test chain-specific quirks here (e.g., StrKey encoding details). Those belong in the per-chain test directory.
• Don't network-call. Conformance tests must be deterministic and offline.

Acceptance criteria

• test/conformance/index.test.ts covering at least 8 conformance properties across all 4 chains.
• Documentation in test/conformance/README.md explaining the contract.
• Tests pass against current main; document any failures as findings (likely Solana, given it shares Stellar primitives).
• When a new chain is added, the developer adds one entry in the chain registry and gets all conformance tests for free.

Files to start with

• sdk/src/chains/{evm,stellar,solana,ckb}/index.ts for the exports surface
• test/chains/*/e2e.test.ts for per-chain reference scenarios

[mitchellecm7]

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

Good day I am a full stack developer with over 6 years of experience and I have previously implemented the integration of cross chain confromance test suite, based on your requirements I'll Create test/conformance/ with a single test file that imports a chain module by name and runs a battery of operations. I have good practical knowledge on this kindly assign this to me

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

[Heazzy500]

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

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

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

[zeemscript]

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

Hi Maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately.

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

[drips-wave]

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

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