Log obfuscation / redaction utility

[truthixify]

Extra labels: privacy, dx
Tier: S (1-2 days) | Type: dx + privacy

Context. Scanner debug logs leak meta-addresses + tx hashes. When a user shares a bug report, they leak scan context. Ship a redaction helper that replaces addresses / hashes with stable pseudonyms.

Scope.

• redact(text: string): string for common Stellar identifiers.
• Also expose as a Vitest reporter plugin so failures print redacted output by default.
• Off by default in production logs (dev signal), on by default in test logs.

Acceptance.

• Every address / tx hash / contract ID in a canned log gets redacted
• Pseudonyms stable across calls (same address → same alias)
• Documented in src/chains/stellar/README.md

Files. src/chains/stellar/log/redact.ts (new), test/chains/stellar/log/redact.test.ts (new).

[Kingvic300]

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

I would love to work on this

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

[drips-wave]

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

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