[Contract-integration note] bridgelet-product-audit/integration-notes/generated-wallet-key-custody.md: Where the secretKey returned by generateNewWallet() is meant to be handled

[phertyameen]

Contract-integration note: bridgelet-product-audit/integration-notes/generated-wallet-key-custody.md

Purpose:
Document the key-custody question raised by this function's existence and current lack of any caller.

This file should cover:

• Note that generateNewWallet() returns a raw secretKey string but is not currently called from any app route or component found in frontend/app or frontend/components.
• Discuss what a safe design would need to specify before this function is wired up: where the secret is stored, whether it's ever transmitted, and how the user recovers it.
• Frame this as an open design question to resolve before this function gets its first caller, not as a currently-exploitable issue given it's unused.

Scope: documentation-only addition to a new, standalone folder. No changes to frontend/ or mobile/ are needed to close this issue.

---

Part of the bridgelet-product-audit/ knowledge-base initiative (20/100).

[AbdulmujibOladayo]

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

I have reviewed this issue and its acceptance criteria carefully. The requirements are clear and well-scoped (large complexity). I have hands-on experience with the required stack and can implement this following the patterns and conventions already in the codebase. I will deliver complete, tested code that satisfies every acceptance criterion without requiring follow-up corrections. I can start immediately and am happy to discuss approach details with the maintainer beforehand.

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@AbdulmujibOladayo's PR #357 was approved and merged by @phertyameen.

🏆 @AbdulmujibOladayo: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,172 total points). Track your full progress on GrantFox.

👏 Great work, @AbdulmujibOladayo! Keep contributing to bridgelet-org.

[drips-wave]

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

😎 @AbdulmujibOladayo: 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.