Standardize WASM build target to wasm32-unknown-unknown in CI and fix wasm32v1-none mismatch

[Jagadeeshftw]

Description

The CI workflow at .github/workflows/contracts.yml currently uses an inconsistent WASM build target, mixing wasm32-unknown-unknown and wasm32v1-none in different job steps. Soroban SDK 23.4.1 requires wasm32-unknown-unknown for contract compilation, and using wasm32v1-none causes linker errors or silently produces incompatible binaries that fail on-network deployment. All CI build steps must be normalized to wasm32-unknown-unknown with the mismatch documented in the build guide.

Requirements and context

• Audit all cargo build and stellar contract build invocations in .github/workflows/contracts.yml for target flags
• Replace all occurrences of wasm32v1-none with wasm32-unknown-unknown
• Update .cargo/config.toml if a default target override exists and is incorrect
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested execution

Fork the repo and create a branch

git checkout -b feature/standardize-wasm-build-target

Implement changes

• Update/Write contract: onchain/contracts/stello_pay_contract/src/lib.rs
• Write comprehensive tests: onchain/contracts/stello_pay_contract/tests/build_target_tests.rs
• Add documentation: docs/build-targets.md
• Include NatSpec-style doc comments
• Validate security assumptions

Test and commit

• Run tests: cargo test -p stello_pay_contract
• Cover edge cases
• Include test output and security notes

Example commit message

feat: standardize WASM build target to wasm32-unknown-unknown across all CI jobs

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[AbuTuraab]

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

Hi,

I’d like to request assignment to this issue.

As a full-stack developer working actively in the Stellar ecosystem, I understand how important robust automation is for projects that combine Soroban smart contracts, backend services, and frontend applications. A reliable CI/CD pipeline is the backbone of safe contract development, deterministic builds, and predictable testnet releases.

During the previous waves of contributions, I worked on several Stellar-related repos where I resolved issues such as:
Frontend implementations.
Misconfigured GitHub Actions leading to failing builds
Missing or incomplete Soroban contract test pipelines
Frontend pipelines that didn’t catch build/lint errors
Inefficient caching (Rust, pnpm) that slowed down CI
Incorrect workflow permissions affecting deployment and artifact uploads
These issues helped me develop a strong sense of what healthy CI/CD should look like for blockchain projects.

Relevant Skills
Full-stack expertise with Soroban, Rust, TypeScript, and modern frontend tooling
Strong experience designing and maintaining GitHub Actions workflows
Familiar with contract testing, reproducible builds, and blockchain dev best practices
Experience with pnpm-based frontend CI pipelines (install, lint, type-check, build)
Comfortable implementing secure deployment flows, secret management, and workflow permission hardening
Confident in making pipelines faster and more reliable using smart caching strategies

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

[drips-wave]

Congratulations, @AbuTuraab! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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

[OsejiFabian]

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

PLEASE I WOULD LIKE TO WORK ON THIS ISSUE .

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

[Arome8240]

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

Can I work on this issue?

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

[drips-wave]

Congratulations, @OsejiFabian! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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