OPPAD OFFICIAL WHITEPAPER
  • 🧠 I. Vision & Foundations
    • 1.Abstract
    • 2.Introduction
    • 3.Market Analysis
    • 4.Problem Statement
  • 5.Solution Overview
  • 🏗️ II. Technical Core & Infrastructure
    • 1.Platform Architecture
      • 1.1.Front-end
      • 1.2.backend
      • 1.3.smart contract overview
    • 2.Security Measures
    • 3.Database
    • 4.Dual Review Mechanism
      • 4.1.AegisAI™ (AI Reviewer Engine)
      • 4.2.Sentinel Review (Manual Process)
      • 4.3.Review Workflow
      • 4.4.Risk Classification System
    • 5.API & Integrations
  • 🚀 III. Launch Engine
    • 1.Presale
    • 2.Fairlaunch
    • 3.Stealth Launch
    • 4.Token Creation
    • 5.OPPADLock
    • 6.Badges
    • 7.Dynamic Whitelists & Participation Settings
    • 8.Built-in KYC & Audit
  • 📕O-Pump Mode™
    • 1.What is O-Pump?
    • 2.How It Works
    • 3.Super Projects
    • 4.Safety First
    • 5.O-Pump vs Others
    • 6.Use Cases
  • 📕 V. OPPAD Economic Engine
    • 1.Staking
    • 2.NFT Passes
    • 3.Farming & Rewards
      • How to Launch a Farm in 3 Steps
    • 4.Revenue Sharing
  • 📘 VI. Governance & Continuity
    • 1.Legal Compliance
    • 2.Error Handling
    • 3.Roadmap
  • 📕OFFICIAL LINKS AND SOCIALS
    • Website
    • Tokenomics
    • Official Telegram Community
    • Github
    • Discord
    • Youtube
    • Tiktok
Powered by GitBook
On this page
  1. 🏗️ II. Technical Core & Infrastructure

3.Database

Efficient, secure, and scalable off-chain data architecture.

While smart contracts handle all on-chain logic (contributions, locks, claims), OPPAD uses a structured database system to manage off-chain metadata, enhance user experience, and power admin tools and analytics. The backend is tightly coupled with smart contract events to ensure synchronization, transparency, and accountability.

🛠️ 1. Architecture Overview

  • Engine: MySQL / MariaDB

  • Environment: Hosted on a secure cloud instance with role-based access

  • Access: Backend services connect via secured queries with sanitation layers

[!INFO] The database does not store any wallet private keys, balances, or sensitive funds. All critical logic is executed via smart contracts.

📦 2. Stored Data Categories

Table Name

Purpose

projects

General info (name, chain, category, logo, status)

applications

Multi-step launch form entries

vesting_schedules

TGE %, unlock intervals, unlock rates

users

Wallets linked to tasks, rewards, staking

referrals

Referral invites, tracking, reward claims

audit_results

AI + manual findings per project

badges

KYC, audit, trust, and lock status records

analytics

Project KPIs, TVL tracking, launch performance

🔄 3. Live Sync with Smart Contracts

  • When users submit a form:  - Data is stored in applications  - Admins trigger review flow

  • When a launch goes live:  - On-chain events trigger projects table update  - Contract addresses, token info, and claim status are updated

  • Vesting and farming logic:  - Reads on-chain state and combines it with off-chain metadata (e.g. image, description)

[!TIP] The database ensures that even if the user is on mobile or using a slow RPC, they still get fast-loading dashboards with real-time progress, token info, and eligibility checks.

🔒 4. Security Controls

  • SQL injection prevention and data sanitation

  • Input validation and data length checks

  • Admin activity logs and change tracking

  • Backup strategy and restore snapshots

[!WARNING] Direct database access is restricted to backend services and internal roles — no client-side interaction is permitted.

Previous2.Security MeasuresNext4.Dual Review Mechanism

Last updated 5 days ago