audit(stellar): initial findings, add audit tests and report skeleton

[Abdulmajeed82]

Closes #1

[drips-wave]

@Abdulmajeed82 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[truthixify]

The audit report (audits/2026-06-author-stellar-module.md) and the reproducer tests in test/audits/stellar.test.ts are what issue #1 needs.

Blocker: branch is from very old main, so the diff currently removes a lot of merged work (RN compat polyfills, JSDoc additions, COMPAT.md, range-scan filters, streaming scan, and more). Net -1261 lines. Could you rebase?

git fetch origin
git rebase origin/develop
# keep only your new files:
#   audits/2026-06-author-stellar-module.md
#   test/audits/stellar.test.ts
# and any small package.json change for the audit test path
# drop all the deletions to src/chains/stellar/*, src/compat/*, test/compat/*, test/chains/stellar/*
git push --force-with-lease

After the rebase the diff should be net-positive only, no deletions of existing files. Then I'll re-review the audit findings themselves and merge. Thanks @Abdulmajeed82.

[truthixify]

The audit doc and reproducer tests survive the merge. Conflicts in 4 files (all from view-tag work in #45 and streaming scan in #34):

• src/chains/stellar/index.ts
• src/chains/stellar/scan.ts
• src/chains/stellar/stealth.ts
• test/chains/stellar/scan.test.ts

git fetch origin
git rebase origin/develop
git push --force-with-lease

For scan.ts / stealth.ts keep develop's new exports (computeAnnouncementViewTag, scanAnnouncementsLegacySharedSecretTag, scanAnnouncementsStream) and graft your audit-related tests on top. For scan.test.ts keep develop's existing tests and add your audit-finding reproducers alongside.

Thanks @Abdulmajeed82.

[truthixify]

Closing as we wrap up this round of the Wraith × Drips × Stellar Wave program.

Thanks for the contribution. The work and review history stays on this PR for reference. A new set of issues will go up shortly under the same Stellar Wave label if you want to pick something fresh next round.

If you specifically want to land the work that's already in this PR (post-wave), feel free to reopen and rebase against develop. Otherwise, no action needed.