Add helper for masking sensitive fields before writing to structured logs

[Chucks1093]

Summary

Callback URLs and wallet addresses occasionally appear in log output when error context is captured naively. A shared masking helper should be applied before any structured log write to ensure sensitive fields never appear in plain text.

Scope

• Add maskSensitive(obj: Record<string, unknown>): Record<string, unknown> helper
• Mask any key matching: url, callback, address, webhook_url, recipient — replace value with [REDACTED]
• Apply the helper in all structured log calls that accept an arbitrary context object
• Add unit tests: masked key present → [REDACTED], unmasked key → value unchanged, nested object → nested keys masked

Acceptance Criteria

• All listed key names masked to [REDACTED]
• Non-sensitive keys unchanged
• Nested objects masked recursively
• Helper applied in all structured log context writes

ETA: 12 hours

---

Coordinate on Telegram

[Songu3020]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[iamkingvalor]

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

please can i work on this?

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

[bandanadivya]

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

Hi
I’d like to work on this issue if it’s available. I’m a full-stack Web2 & Web3 developer with solid open-source experience and can start working on it right away.

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

[Chuks-coderr]

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

hello i would like to work on this project

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @Chuks-coderr as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Chuks-coderr: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.