scripts/invoke.mjs accepts the signer's secret key as a plain CLI argument

[chonilius]

Same issue as scripts/deploy.mjs's sibling: scripts/invoke.mjs reads the secret key from process.argv[2] per its usage line (Usage: node invoke.mjs <secret> <contractId> <method> [args...]), which is even more exposed in practice since invoke.mjs is the script used for every subsequent contract call (including initialize, and per README's example, release-style admin calls) — not just a one-time deploy. Every invocation leaks the admin/oracle key into shell history and process listings. Same fix direction: environment variable or masked interactive prompt instead of an argv position.

[sulaimonifeoluwa4-blip]

@sulaimonifeoluwa4-blip has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi can I work on this

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

[toxxxxicc]

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

hello miantainer, i would like to work on this

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

[drips-wave]

Congratulations, @toxxxxicc! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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