Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    WalletConnect Project ID (Reown Cloud)

    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 keyClassBuyer writable?
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_IDpublic (NEXT_PUBLIC_*)Yes — public_shared on Secrets

    Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).

    Obtain a Project ID

    1. 1

      Open Reown Cloud and sign in (GitHub / email).

    2. 2

      Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.

    3. 3

      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.

    4. 4

      In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.

    5. 5

      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.

    Why members need this

    • Desktop MetaMask extension — works without WalletConnect (injected connector).
    • Phone wallets (Trust, Rainbow, MetaMask mobile) — need WalletConnect QR / deep link → requires your Project ID.
    • Console warning “No valid project ID found. WalletConnect disabled” means the env key is missing or invalid on that deploy.

    Ethereum wallets overview

    Wagmi stack, connectors, and RPC checklist.

    Public vars

    Other NEXT_PUBLIC_* keys on the same Secrets tab.

    Supported services

    Full third-party account catalog for go-live.

    Runtime gate (verified)

    Template comment SSOT (env.local.template):

    Ownership: PUBLIC_SHARED_EXACT in features/crm/lab/env-key-ownership.ts — buyers may PATCH via /api/my-orders/[id]/env.

    Connector behavior (docs + Wagmi config pattern): WalletConnect is added only when the project ID is present and not the demo-project-id placeholder — avoids WalletConnect Cloud 403 responses. See Ethereum wallets.

    Smoke test

    1. Deploy with Project ID set.
    2. Hit a pathNeedsWeb3() route (/auth/wallet-connect, /wallet, /nft, …).
    3. Connector list includes WalletConnect; QR flow opens without “No valid project ID” console warning.

    Related documentation

    Related documentation

    Ethereum wallets (Wagmi v3)

    Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.

    Order Lab secrets

    Same-workflow: save on Secrets and apply on next deploy.

    Public environment variables

    See-also: other buyer public_shared keys.

    Wallet & Credit System

    Next-step: custodial wallet product surface after connect.

    Project configuration

    WalletConnect Project ID (Reown Cloud)

    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 keyClassBuyer writable?
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_IDpublic (NEXT_PUBLIC_*)Yes — public_shared on Secrets

    Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).

    Obtain a Project ID

    1. 1

      Open Reown Cloud and sign in (GitHub / email).

    2. 2

      Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.

    3. 3

      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.

    4. 4

      In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.

    5. 5

      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.

    Why members need this

    • Desktop MetaMask extension — works without WalletConnect (injected connector).
    • Phone wallets (Trust, Rainbow, MetaMask mobile) — need WalletConnect QR / deep link → requires your Project ID.
    • Console warning “No valid project ID found. WalletConnect disabled” means the env key is missing or invalid on that deploy.

    Ethereum wallets overview

    Wagmi stack, connectors, and RPC checklist.

    Public vars

    Other NEXT_PUBLIC_* keys on the same Secrets tab.

    Supported services

    Full third-party account catalog for go-live.

    Runtime gate (verified)

    Template comment SSOT (env.local.template):

    Ownership: PUBLIC_SHARED_EXACT in features/crm/lab/env-key-ownership.ts — buyers may PATCH via /api/my-orders/[id]/env.

    Connector behavior (docs + Wagmi config pattern): WalletConnect is added only when the project ID is present and not the demo-project-id placeholder — avoids WalletConnect Cloud 403 responses. See Ethereum wallets.

    Smoke test

    1. Deploy with Project ID set.
    2. Hit a pathNeedsWeb3() route (/auth/wallet-connect, /wallet, /nft, …).
    3. Connector list includes WalletConnect; QR flow opens without “No valid project ID” console warning.

    Related documentation

    Related documentation

    Ethereum wallets (Wagmi v3)

    Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.

    Order Lab secrets

    Same-workflow: save on Secrets and apply on next deploy.

    Public environment variables

    See-also: other buyer public_shared keys.

    Wallet & Credit System

    Next-step: custodial wallet product surface after connect.

    Project configuration

    WalletConnect Project ID (Reown Cloud)

    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 keyClassBuyer writable?
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_IDpublic (NEXT_PUBLIC_*)Yes — public_shared on Secrets

    Paste it on Order Lab Secrets: ?tab=secrets (your order id will differ).

    Obtain a Project ID

    1. 1

      Open Reown Cloud and sign in (GitHub / email).

    2. 2

      Create a new project. Choose the AppKit / WalletConnect product type offered for web dapps.

    3. 3

      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.

    4. 4

      In Order Lab → Secrets, find NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID, paste the ID, and Save.

    5. 5

      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.

    Why members need this

    • Desktop MetaMask extension — works without WalletConnect (injected connector).
    • Phone wallets (Trust, Rainbow, MetaMask mobile) — need WalletConnect QR / deep link → requires your Project ID.
    • Console warning “No valid project ID found. WalletConnect disabled” means the env key is missing or invalid on that deploy.

    Ethereum wallets overview

    Wagmi stack, connectors, and RPC checklist.

    Public vars

    Other NEXT_PUBLIC_* keys on the same Secrets tab.

    Supported services

    Full third-party account catalog for go-live.

    Runtime gate (verified)

    Template comment SSOT (env.local.template):

    Ownership: PUBLIC_SHARED_EXACT in features/crm/lab/env-key-ownership.ts — buyers may PATCH via /api/my-orders/[id]/env.

    Connector behavior (docs + Wagmi config pattern): WalletConnect is added only when the project ID is present and not the demo-project-id placeholder — avoids WalletConnect Cloud 403 responses. See Ethereum wallets.

    Smoke test

    1. Deploy with Project ID set.
    2. Hit a pathNeedsWeb3() route (/auth/wallet-connect, /wallet, /nft, …).
    3. Connector list includes WalletConnect; QR flow opens without “No valid project ID” console warning.

    Related documentation

    Related documentation

    Ethereum wallets (Wagmi v3)

    Deep-dive: Wagmi connectors, RPC SSOT, and white-label picker.

    Order Lab secrets

    Same-workflow: save on Secrets and apply on next deploy.

    Public environment variables

    See-also: other buyer public_shared keys.

    Wallet & Credit System

    Next-step: custodial wallet product surface after connect.

    Project configuration

    Prerequisite: project configuration hub.

    bash
    
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=

    Prerequisite: project configuration hub.

    bash
    
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=

    Prerequisite: project configuration hub.

    bash
    
# WalletConnect / Reown Cloud project ID (https://cloud.reown.com)
NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID=
    1. Docs
    2. /Project configuration
    3. /WalletConnect Project ID (Reown Cloud)
    Updated Aug 7, 20262 min listen
    1. Docs
    2. /Project configuration
    3. /WalletConnect Project ID (Reown Cloud)
    Updated Aug 7, 20262 min listen
    1. Docs
    2. /Project configuration
    3. /WalletConnect Project ID (Reown Cloud)
    Updated Aug 7, 20262 min listen