CI pins the Rust toolchain to the floating stable tag rather than a fixed version

[chonilius]

.github/workflows/ci.yml uses dtolnay/rust-toolchain@stable for both the test and wasm-build jobs, which resolves to whatever the current Rust stable release is at the time each workflow run executes — not a fixed version. This means a PR that changes nothing Rust-toolchain-related can start failing CI (a new clippy lint firing, a rustfmt style change) purely because Rust itself updated between when the PR was opened and when CI last ran, with no way to distinguish "this PR broke something" from "upstream Rust changed." Pinning to a specific version (ideally sourced from the already-proposed rust-toolchain.toml, so there's one source of truth) would make CI failures attributable to the actual diff again.

[malaysiaonelove]

Hi maintain,I will love to work on this issue,I have an experience and I have already reviewed the issue please assigned me to it and I will give a good result.

[supreme2580]

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

Hello maintainer, can I be assigned to this issue?

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

[MorsH14]

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

Hi @maintainer, I’d like to take this on! I’ve reviewed the issue description and located the relevant code section. Could you please assign this to me? I can submit a PR within 3hrs

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

[Daniel202251]

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

I’m a smart contract and full-stack developer who turns complex ideas into secure, production-ready blockchain code.
With strong skills in Rust and Solidity, I build systems that are fast, safe, and built to last.
My experience with the Stellar SDK lets me ship real-world Web3 solutions that actually move value

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

[karanjadavi]

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

can i work on this issue

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

[kulayddon]

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

Will like to work on this please

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

[drips-wave]

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

🧑‍💻 @kulayddon: 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 @kulayddon as part of the Stellar Wave Program's 8th Wave 🥳

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