OpportunitiesEntities
Docs
    Ring Platform

    Decentralized Self-building Future

    Sign In
    Entities
    Opportunities
    Store
    Docs
    Platform Concepts
    RING EconomySonoratek LLCGlobal ImpactAI Meets Web3
    Get Started
    Quick StartCalculatorRoadmap
    Privacy|Contact
    v1.104.21|Sonoratek LLC

    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 Logo

    Loading documentation...

    Preparing Ring content

    Ring Logo

    Loading documentation...

    Preparing Ring content

    Ring Logo

    Loading documentation...

    Preparing Ring content

    Credit Rewards

    Ring awards credit balance units (credit.creditUnitLabel, e.g. points on ring-platform.org) when users complete real contribution. Credits are platform utility (spendable for store, membership, generative media) — not speculative crypto. Earn rules are deterministic, capped, and auditable.

    Config SSOT

    Write path: ring-config.json → credit.rewards

    json
    
    {
      "credit": {
        "creditUnitLabel": "points",
        "creditBalanceUnitToMainCurrency": 1,
        "rewards": {
          "minRole": "subscriber",
          "multipliers": { "subscriber": 1, "member": 1.5, "confidential": 2 },
          "dailyEarnCap": { "subscriber": 50, "member": 100, "confidential": 150 },
          "events": {
            "adminVerify": { "amount": "50", "enabled": true, "idempotencyMode": "once_per_user" },
            "commentCreated": { "amount": "2", "idempotencyMode": "once_per_object" }
          }
        }
      }
    }

    Read fallback order (migration): credit.rewards.events → credit.creditAddEvents → credits.rewards.events.

    Idempotency

    ModeKeyUse
    once_per_usercredit_add_event:{trigger}:{userId}Profile fields, KYC, completion bonus
    once_per_object…:{objectType}:{objectId}Comments, reviews, approved news

    Unique index on credit_add_events.idempotency_key prevents races.

    Role multipliers & daily caps

    Final award = floor(base × multiplier) (minimum 1 if base ≥ 1). Daily cap is UTC calendar day; if the award would exceed remaining budget, the entire award is skipped (skip_reason: daily_cap) — never partial-minted.

    Visitors earn nothing (minRole: subscriber).

    Engine

    enqueueRewardCreditAddEvent in lib/wallet/reward-credit-service.ts:

    1. Load rule → enabled / minRole / username / verified gates
    2. Build idempotency key → existing completed → existing
    3. Multiplier + UTC daily cap
    4. creditBalanceService.addCredits(..., 'reward_credit_add', getFiatCreditAccountingRate())
    5. Audit row + appendEvent('reward_credit_add')

    Ledger failures → status failed (not skipped).

    Wired actions (Phase 1)

    TriggerWhen
    Profile fields / profileCompletedAfter updateProfile empty→filled / completeness
    adminVerifyAdmin KYC verification
    newsStoryApprovedMain-page approval for user-authored articles
    commentCreated / reviewCreated / requestCreatedAfter create (once per object id)

    profileCompleted is a completion bonus in addition to field awards.

    Admin monitoring

    • /admin/rewards — charts (daily mint, by trigger, by role, top earners)
    • Users activity tab Rewards
    • APIs under /api/admin/rewards/*

    Ethics

    No chance mechanics, no client-trusted amounts, published rules, affiliate token rail stays separate. See LegioX lens ua_non_speculative_reputation_wealth_designer.

    1. Docs
    2. /Features
    3. /Credit Rewards

    2 min listen

    Credit Rewards

    Ring awards credit balance units (credit.creditUnitLabel, e.g. points on ring-platform.org) when users complete real contribution. Credits are platform utility (spendable for store, membership, generative media) — not speculative crypto. Earn rules are deterministic, capped, and auditable.

    Config SSOT

    Write path: ring-config.json → credit.rewards

    json
    
    {
      "credit": {
        "creditUnitLabel": "points",
        "creditBalanceUnitToMainCurrency": 1,
        "rewards": {
          "minRole": "subscriber",
          "multipliers": { "subscriber": 1, "member": 1.5, "confidential": 2 },
          "dailyEarnCap": { "subscriber": 50, "member": 100, "confidential": 150 },
          "events": {
            "adminVerify": { "amount": "50", "enabled": true, "idempotencyMode": "once_per_user" },
            "commentCreated": { "amount": "2", "idempotencyMode": "once_per_object" }
          }
        }
      }
    }

    Read fallback order (migration): credit.rewards.events → credit.creditAddEvents → credits.rewards.events.

    Idempotency

    ModeKeyUse
    once_per_usercredit_add_event:{trigger}:{userId}Profile fields, KYC, completion bonus
    once_per_object…:{objectType}:{objectId}Comments, reviews, approved news

    Unique index on credit_add_events.idempotency_key prevents races.

    Role multipliers & daily caps

    Final award = floor(base × multiplier) (minimum 1 if base ≥ 1). Daily cap is UTC calendar day; if the award would exceed remaining budget, the entire award is skipped (skip_reason: daily_cap) — never partial-minted.

    Visitors earn nothing (minRole: subscriber).

    Engine

    enqueueRewardCreditAddEvent in lib/wallet/reward-credit-service.ts:

    1. Load rule → enabled / minRole / username / verified gates
    2. Build idempotency key → existing completed → existing
    3. Multiplier + UTC daily cap
    4. creditBalanceService.addCredits(..., 'reward_credit_add', getFiatCreditAccountingRate())
    5. Audit row + appendEvent('reward_credit_add')

    Ledger failures → status failed (not skipped).

    Wired actions (Phase 1)

    TriggerWhen
    Profile fields / profileCompletedAfter updateProfile empty→filled / completeness
    adminVerifyAdmin KYC verification
    newsStoryApprovedMain-page approval for user-authored articles
    commentCreated / reviewCreated / requestCreatedAfter create (once per object id)

    profileCompleted is a completion bonus in addition to field awards.

    Admin monitoring

    • /admin/rewards — charts (daily mint, by trigger, by role, top earners)
    • Users activity tab Rewards
    • APIs under /api/admin/rewards/*

    Ethics

    No chance mechanics, no client-trusted amounts, published rules, affiliate token rail stays separate. See LegioX lens ua_non_speculative_reputation_wealth_designer.

    1. Docs
    2. /Features
    3. /Credit Rewards

    2 min listen

    Credit Rewards

    Ring awards credit balance units (credit.creditUnitLabel, e.g. points on ring-platform.org) when users complete real contribution. Credits are platform utility (spendable for store, membership, generative media) — not speculative crypto. Earn rules are deterministic, capped, and auditable.

    Config SSOT

    Write path: ring-config.json → credit.rewards

    json
    
    {
      "credit": {
        "creditUnitLabel": "points",
        "creditBalanceUnitToMainCurrency": 1,
        "rewards": {
          "minRole": "subscriber",
          "multipliers": { "subscriber": 1, "member": 1.5, "confidential": 2 },
          "dailyEarnCap": { "subscriber": 50, "member": 100, "confidential": 150 },
          "events": {
            "adminVerify": { "amount": "50", "enabled": true, "idempotencyMode": "once_per_user" },
            "commentCreated": { "amount": "2", "idempotencyMode": "once_per_object" }
          }
        }
      }
    }

    Read fallback order (migration): credit.rewards.events → credit.creditAddEvents → credits.rewards.events.

    Idempotency

    ModeKeyUse
    once_per_usercredit_add_event:{trigger}:{userId}Profile fields, KYC, completion bonus
    once_per_object…:{objectType}:{objectId}Comments, reviews, approved news

    Unique index on credit_add_events.idempotency_key prevents races.

    Role multipliers & daily caps

    Final award = floor(base × multiplier) (minimum 1 if base ≥ 1). Daily cap is UTC calendar day; if the award would exceed remaining budget, the entire award is skipped (skip_reason: daily_cap) — never partial-minted.

    Visitors earn nothing (minRole: subscriber).

    Engine

    enqueueRewardCreditAddEvent in lib/wallet/reward-credit-service.ts:

    1. Load rule → enabled / minRole / username / verified gates
    2. Build idempotency key → existing completed → existing
    3. Multiplier + UTC daily cap
    4. creditBalanceService.addCredits(..., 'reward_credit_add', getFiatCreditAccountingRate())
    5. Audit row + appendEvent('reward_credit_add')

    Ledger failures → status failed (not skipped).

    Wired actions (Phase 1)

    TriggerWhen
    Profile fields / profileCompletedAfter updateProfile empty→filled / completeness
    adminVerifyAdmin KYC verification
    newsStoryApprovedMain-page approval for user-authored articles
    commentCreated / reviewCreated / requestCreatedAfter create (once per object id)

    profileCompleted is a completion bonus in addition to field awards.

    Admin monitoring

    • /admin/rewards — charts (daily mint, by trigger, by role, top earners)
    • Users activity tab Rewards
    • APIs under /api/admin/rewards/*

    Ethics

    No chance mechanics, no client-trusted amounts, published rules, affiliate token rail stays separate. See LegioX lens ua_non_speculative_reputation_wealth_designer.

    1. Docs
    2. /Features
    3. /Credit Rewards

    2 min listen