WalletConnect project ID defaults to empty string, breaking pairing

[therealjhay]

ProblemNEXT_PUBLIC_WALLETCONNECT_PROJECT_ID || '' means without explicit configuration the client attempts to pair against the public relay with an empty project id, which the relay rejects — yet the UI proceeds to display a QR code as if pairing is viable.

1. The empty-string default is indistinguishable from "misconfigured" and gives no user-facing error.
2. Only a QR code is shown; there is no indication that pairing will fail until the wallet fails to settle.
3. README/.env.example do not document the requirement.

Solution

• Treat a missing/empty project id as a hard configuration error and surface it in the connect modal.
• Add env documentation and a dev-mode warning.
• Provide a graceful "configuration not set" state instead of an unworkable QR code.

Acceptance Criteria

• Without the project id, the wallet modal shows a clear configuration error instead of a dead QR.
• README documents the var and an example value source.
• With the var set, pairing proceeds as before.
• npm run build passes.

Note for Contributors: Write a clear PR description. Include screenshot of the config-error state and the documented var in README.

[VeronicDev]

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

Hi, I can fix this pls assign

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

[payfoxX]

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

I love to fix this issue, kindly assign it to me. Thanks

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

[Muyideen-js]

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

Hi, I can fix this

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

[dollfins]

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

hello maintainer, can i work on this issue

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

[zuru122]

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

Can I work on this issues

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

[drips-wave]

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

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