[Wave 6 10/10] Strict environment validation across services and frontend builds

[karagozemin]

Summary

Add strict environment validation for coordinator, resolver, relayer, and frontend builds so misconfigured testnet/mainnet deployments fail fast.

Context

• Multiple packages read deployment-critical env vars directly from process.env or Vite envs.
• Mainnet is intentionally disabled until audit, so accidental VITE_MAINNET_ENABLED=true or missing testnet contract ids should be obvious in CI/deploy logs.
• The coordinator already depends on zod; a shared validation pattern can reduce runtime surprises.

Scope

• Add env schema validation to coordinator and resolver startup.
• Add frontend build-time checks for required testnet config and guarded mainnet enablement.
• Add relayer validation for RPC URL, contract address, and timeout variables used by health/refund paths.
• Document required env vars in env.example or package READMEs.

Acceptance criteria

• Each service fails at startup/build with a clear error when required env vars are missing or malformed.
• Mainnet enablement requires an explicit audited/deployment confirmation variable, not only VITE_MAINNET_ENABLED=true.
• Tests or smoke scripts cover at least one invalid env case per affected package.
• Env documentation is updated in one canonical place.

Pointers

• coordinator/src/config.ts
• resolver/src/config.ts
• relayer/src/index.ts
• relayer/src/phase6-bridge-service.ts
• frontend/src/config/networks.ts
• env.example
• docs/DEPLOYMENT.md

Complexity

Medium (configuration safety across packages)

[nikkybel]

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

please can i be assigned this issue?

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

[drips-wave]

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

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

[Terrajlz]

I'd like to work on this.

Recent work:

• Nobay Protocol: 21/21 Hardhat tests passing, 15-finding security audit, full OZ v5 migration
• DeXe Protocol: identified High-severity tx.origin vulnerability in PoolFactory (SWC-115)
• Audited contracts across Aave V3, GMX, Uniswap V3, MakerDAO, Lido, ENS, Ethena

I can deliver clean, tested code with security audit. Turnaround: 24 hours. Ready to start immediately.