Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Documentation

    Welcome — mission & audiences

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Library hub

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Getting Started

    Index
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps

    Architecture

    Index
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM Architecture
    PaymentConductor architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Security

    Features

    Platform Features
    Authentication
    Email AI-CRM System
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Web3 Wallet
    Multi-Vendor Store
    Payment Integration
    PaymentConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience

    API

    Index
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet
    Store API

    CLI

    Ring CLI (enterprise only)

    Customization

    Index
    Branding
    Features
    Localization
    Themes
    Components

    Deployment

    Index
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery

    Development

    Index
    Local Setup
    Code Structure
    Community tooling
    Ring MCP Server
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices

    Examples

    Index
    Quick Start
    Authentication
    Email AI-CRM Tutorial
    Api Integration
    Web3 Integration
    White Label
    Real World

    Integrations

    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Library hub
    Welcome — mission & audiences
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP
    Deploy (Docker · k8s)
    Security & compliance reads
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Documentation

    Welcome — mission & audiences

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Library hub

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Getting Started

    Index
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps

    Architecture

    Index
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM Architecture
    PaymentConductor architecture
    News Kingdom architecture
    Proxy and internationalization

    Features

    Platform Features
    Authentication
    Email AI-CRM System
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Web3 Wallet

    API

    Index
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet
    Store API

    CLI

    Ring CLI (enterprise only)

    Customization

    Index
    Branding
    Features
    Localization
    Themes
    Components

    Deployment

    Index
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery

    Development

    Index
    Local Setup
    Code Structure
    Community tooling
    Ring MCP Server
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices

    Examples

    Index
    Quick Start
    Authentication
    Email AI-CRM Tutorial
    Api Integration
    Web3 Integration
    White Label
    Real World

    Integrations

    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Library hub
    Welcome — mission & audiences
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP
    Deploy (Docker · k8s)
    Security & compliance reads
    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Documentation

    Welcome — mission & audiences

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Library hub

    Welcome to Ring Platform - Gateway Between Humanity and the Quantum World

    Getting Started

    Index
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps

    Architecture

    Index
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM Architecture
    PaymentConductor architecture
    News Kingdom architecture
    Proxy and internationalization

    Features

    Platform Features
    Authentication
    Email AI-CRM System
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Web3 Wallet

    API

    Index
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet
    Store API

    CLI

    Ring CLI (enterprise only)

    Customization

    Index
    Branding
    Features
    Localization
    Themes
    Components

    Deployment

    Index
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery

    Development

    Index
    Local Setup
    Code Structure
    Community tooling
    Ring MCP Server
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices

    Examples

    Index
    Quick Start
    Authentication
    Email AI-CRM Tutorial
    Api Integration
    Web3 Integration
    White Label
    Real World

    Integrations

    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Library hub
    Welcome — mission & audiences
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP
    Deploy (Docker · k8s)
    Security & compliance reads
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Admin API
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    Api Examples
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Real Time
    Security
    Multi-Vendor Store
    Payment Integration
    PaymentConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Admin API
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    Api Examples
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Real Time
    Security
    Multi-Vendor Store
    Payment Integration
    PaymentConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Admin API
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    Api Examples
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Ethereum wallets (Wagmi v3)

    Ring ships Wagmi v3 and viem 2.x with a custom connector picker and account menu (no @rainbow-me/rainbowkit). Multi-wallet support comes from Wagmi connectors configured in lib/wagmi-config.ts.

    Default connectors

    Typical production lineup (exact list is in your clone’s getConnectors()):

    1. injected() — browser extensions and EIP-6963 discovery where available.
    2. metaMask() — explicit MetaMask connector (install peer @metamask/connect-evm).
    3. coinbaseWallet({ appName, appLogoUrl }) — install peer @coinbase/wallet-sdk.
    4. walletConnect({ projectId, metadata, showQrModal }) — mobile and broad wallet support (install peer @walletconnect/ethereum-provider), only if NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set and not a placeholder.

    WalletConnect is omitted when the project ID is missing to avoid 403 responses from WalletConnect Cloud.

    Environment variables

    VariablePurpose
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID

    Ethereum wallets (Wagmi v3)

    Ring ships Wagmi v3 and viem 2.x with a custom connector picker and account menu (no @rainbow-me/rainbowkit). Multi-wallet support comes from Wagmi connectors configured in lib/wagmi-config.ts.

    Default connectors

    Typical production lineup (exact list is in your clone’s getConnectors()):

    1. injected() — browser extensions and EIP-6963 discovery where available.
    2. metaMask() — explicit MetaMask connector (install peer @metamask/connect-evm).
    3. coinbaseWallet({ appName, appLogoUrl }) — install peer @coinbase/wallet-sdk.
    4. walletConnect({ projectId, metadata, showQrModal }) — mobile and broad wallet support (install peer @walletconnect/ethereum-provider), only if NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set and not a placeholder.

    WalletConnect is omitted when the project ID is missing to avoid 403 responses from WalletConnect Cloud.

    Environment variables

    VariablePurpose
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID

    Ethereum wallets (Wagmi v3)

    Ring ships Wagmi v3 and viem 2.x with a custom connector picker and account menu (no @rainbow-me/rainbowkit). Multi-wallet support comes from Wagmi connectors configured in lib/wagmi-config.ts.

    Default connectors

    Typical production lineup (exact list is in your clone’s getConnectors()):

    1. injected() — browser extensions and EIP-6963 discovery where available.
    2. metaMask() — explicit MetaMask connector (install peer @metamask/connect-evm).
    3. coinbaseWallet({ appName, appLogoUrl }) — install peer @coinbase/wallet-sdk.
    4. walletConnect({ projectId, metadata, showQrModal }) — mobile and broad wallet support (install peer @walletconnect/ethereum-provider), only if NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID is set and not a placeholder.

    WalletConnect is omitted when the project ID is missing to avoid 403 responses from WalletConnect Cloud.

    Environment variables

    VariablePurpose
    NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID
    WalletConnect Cloud projectId (WalletConnect Cloud). Required for QR / deep-link flows.

    RPC URLs for viem http() transports use public defaults unless you customize transports in wagmi-config.

    Wagmi v3 usage patterns

    WalletConnect Cloud projectId (WalletConnect Cloud). Required for QR / deep-link flows.

    RPC URLs for viem http() transports use public defaults unless you customize transports in wagmi-config.

    Wagmi v3 usage patterns

    WalletConnect Cloud projectId (WalletConnect Cloud). Required for QR / deep-link flows.

    RPC URLs for viem http() transports use public defaults unless you customize transports in wagmi-config.

    Wagmi v3 usage patterns

    • Prefer useConnection() for address, chain, isConnected, and related state.
    • List connectors with useConnectors() (not useConnect().connectors).
    • Connect with const c = useConnect(); c.mutate({ connector }) or mutateAsync when you need the hash in scope.
    • Switch chains with useSwitchChain().mutate({ chainId }).
    • Configured chains for UI: useChains() (avoids duplicating chain metadata).
    • Prefer useConnection() for address, chain, isConnected, and related state.
    • List connectors with useConnectors() (not useConnect().connectors).
    • Connect with const c = useConnect(); c.mutate({ connector }) or mutateAsync when you need the hash in scope.
    • Switch chains with useSwitchChain().mutate({ chainId }).
    • Configured chains for UI: useChains() (avoids duplicating chain metadata).
    • Prefer useConnection() for address, chain, isConnected, and related state.
    • List connectors with useConnectors() (not useConnect().connectors).
    • Connect with const c = useConnect(); c.mutate({ connector }) or mutateAsync when you need the hash in scope.
    • Switch chains with useSwitchChain().mutate({ chainId }).
    • Configured chains for UI: useChains() (avoids duplicating chain metadata).

    Official migration reference: Migrate from v2 to v3.

    SSR and persistence

    createConfig uses ssr: true where noted in the codebase. Ring Platform’s canonical app also uses cookie storage so server-rendered pages can hydrate wallet state consistently (cookieStorage + createStorage in wagmi-config.ts). Clones without that wrapper may still run client-only Web3 providers; align with your layout’s dynamic import strategy.

    White-label: changing connectors

    Official migration reference: Migrate from v2 to v3.

    SSR and persistence

    createConfig uses ssr: true where noted in the codebase. Ring Platform’s canonical app also uses cookie storage so server-rendered pages can hydrate wallet state consistently (cookieStorage + createStorage in wagmi-config.ts). Clones without that wrapper may still run client-only Web3 providers; align with your layout’s dynamic import strategy.

    White-label: changing connectors

    Official migration reference: Migrate from v2 to v3.

    SSR and persistence

    createConfig uses ssr: true where noted in the codebase. Ring Platform’s canonical app also uses cookie storage so server-rendered pages can hydrate wallet state consistently (cookieStorage + createStorage in wagmi-config.ts). Clones without that wrapper may still run client-only Web3 providers; align with your layout’s dynamic import strategy.

    White-label: changing connectors

    1. Edit lib/wagmi-config.ts — add or remove connectors from @wagmi/connectors / wagmi/connectors.
    2. Install each connector’s documented peer dependencies only for connectors you enable.
    3. Adjust branding (appName, appLogoUrl, WalletConnect metadata) for your domain.
    4. The connector picker lists useConnectors() output; if you see duplicate EIP-6963 entries, dedupe by connector.id in the picker component (Ring’s default picker already dedupes by id).
    1. Edit lib/wagmi-config.ts — add or remove connectors from @wagmi/connectors / wagmi/connectors.
    2. Install each connector’s documented peer dependencies only for connectors you enable.
    3. Adjust branding (appName, appLogoUrl, WalletConnect metadata) for your domain.
    4. The connector picker lists useConnectors() output; if you see duplicate EIP-6963 entries, dedupe by connector.id in the picker component (Ring’s default picker already dedupes by id).
    1. Edit lib/wagmi-config.ts — add or remove connectors from @wagmi/connectors / wagmi/connectors.
    2. Install each connector’s documented peer dependencies only for connectors you enable.
    3. Adjust branding (appName, appLogoUrl, WalletConnect metadata) for your domain.
    4. The connector picker lists useConnectors() output; if you see duplicate EIP-6963 entries, dedupe by connector.id in the picker component (Ring’s default picker already dedupes by id).

    Security notes

    • Do not expose server secrets to the client bundle.
    • Treat NEXT_PUBLIC_* RPC keys as public: anyone can read them from the browser.

    Related

    • Legacy examples page (ethers-era) was retired — see Web3 integration (redirect) for the pointer only.

    Security notes

    • Do not expose server secrets to the client bundle.
    • Treat NEXT_PUBLIC_* RPC keys as public: anyone can read them from the browser.

    Related

    • Legacy examples page (ethers-era) was retired — see Web3 integration (redirect) for the pointer only.

    Security notes

    • Do not expose server secrets to the client bundle.
    • Treat NEXT_PUBLIC_* RPC keys as public: anyone can read them from the browser.

    Related

    • Legacy examples page (ethers-era) was retired — see Web3 integration (redirect) for the pointer only.