Loading documentation...
Preparing Ring content
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Preparing Ring content
Preparing Ring content
Preparing Ring content
Ring enables WalletConnect only when NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set to a real Reown Cloud project ID (not empty, not the demo placeholder). Without it, injected wallets (MetaMask extension) still work; mobile QR / WalletConnect stays disabled.
WalletConnect (now under Reown Cloud) issues a Project ID that identifies your dapp to the WalletConnect relay. Ring reads that ID from env and wires the Wagmi walletConnect connector when present.
| Env key | Class | Buyer writable? |
|---|---|---|
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID | public (NEXT_PUBLIC_*) | Yes — public_shared on Secrets |
Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).
Open Reown Cloud and sign in (GitHub / email).
Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.
Copy the Project ID (a long hex string). Treat it as public configuration — it is not a private API secret, but it should still be your project, not a shared demo ID.
In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.
Ask your integrator to deploy. After rollout, open a wallet route (login wallet connect, /wallet, NFT, checkout) and confirm WalletConnect / QR appears in the connector picker.
Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.
Same-workflow: save on Secrets and apply on next deploy.
See-also: other buyer public_shared keys.
Next-step: custodial wallet product surface after connect.
Ring enables WalletConnect only when NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set to a real Reown Cloud project ID (not empty, not the demo placeholder). Without it, injected wallets (MetaMask extension) still work; mobile QR / WalletConnect stays disabled.
WalletConnect (now under Reown Cloud) issues a Project ID that identifies your dapp to the WalletConnect relay. Ring reads that ID from env and wires the Wagmi walletConnect connector when present.
| Env key | Class | Buyer writable? |
|---|---|---|
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID | public (NEXT_PUBLIC_*) | Yes — public_shared on Secrets |
Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).
Open Reown Cloud and sign in (GitHub / email).
Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.
Copy the Project ID (a long hex string). Treat it as public configuration — it is not a private API secret, but it should still be your project, not a shared demo ID.
In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.
Ask your integrator to deploy. After rollout, open a wallet route (login wallet connect, /wallet, NFT, checkout) and confirm WalletConnect / QR appears in the connector picker.
Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.
Same-workflow: save on Secrets and apply on next deploy.
See-also: other buyer public_shared keys.
Next-step: custodial wallet product surface after connect.
Ring enables WalletConnect only when NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set to a real Reown Cloud project ID (not empty, not the demo placeholder). Without it, injected wallets (MetaMask extension) still work; mobile QR / WalletConnect stays disabled.
WalletConnect (now under Reown Cloud) issues a Project ID that identifies your dapp to the WalletConnect relay. Ring reads that ID from env and wires the Wagmi walletConnect connector when present.
| Env key | Class | Buyer writable? |
|---|---|---|
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID | public (NEXT_PUBLIC_*) | Yes — public_shared on Secrets |
Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).
Open Reown Cloud and sign in (GitHub / email).
Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.
Copy the Project ID (a long hex string). Treat it as public configuration — it is not a private API secret, but it should still be your project, not a shared demo ID.
In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.
Ask your integrator to deploy. After rollout, open a wallet route (login wallet connect, /wallet, NFT, checkout) and confirm WalletConnect / QR appears in the connector picker.
Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.
Same-workflow: save on Secrets and apply on next deploy.
See-also: other buyer public_shared keys.
Next-step: custodial wallet product surface after connect.
Prerequisite: project configuration hub.
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=Prerequisite: project configuration hub.
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=Prerequisite: project configuration hub.
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=