Architecture Overview
Ridera Protocol — End-to-End System Architecture
Off-Chain Verification → Standardization → On-Chain Settlement → Yield Distribution
🚀 Introduction
Ridera’s architecture is a hybrid off-chain + on-chain system designed to reliably convert global mobility earnings into standardized on-chain financial primitives.
The system is composed of four major layers:
Submission Layer — Workers upload earnings
Verification Layer (Oracle) — Authenticity + fraud checks
Standardization Layer (SRU Engine) — Converts to SRU
Settlement Layer (Base Chain) — Proof storage + yield distribution
This layered architecture ensures:
trust minimization
cryptographic verifiability
transparency
global scalability
economic safety
🧱 High-Level Architecture
1. Submission Layer (Off-Chain)
The entry point for global mobility earnings.
Inputs Supported
Screenshots (OCR)
PDF earnings statements
Weekly payout summaries
Multi-platform logs
Bulk fleet uploads
Responsibilities
Input validation
Parsing & metadata extraction
Secure upload pipeline
Preparing proofs for the Oracle
2. Verification Layer — Ridera Oracle (Off-Chain)
The Oracle ensures every earning submission is:
real
tamper-free
timestamp-valid
region-consistent
non-duplicated
Key Components
OCR Parser
Platform Structure Validator
Timestamp Validation Engine
Region Anomaly Model
Duplicate Detection
ML-Based Fraud Detection
Validator Routing System
Only verified proofs progress to the SRU Engine.
3. Standardization Layer — SRU Engine (Off-Chain)
All verified earnings are converted into SRU (Standardized Revenue Units).
Inputs
validated earnings
platform type
country weighting
worker category
performance factors
Outputs
per-user SRU
total SRU per cycle
SRU metadata
standardized earnings batches
SRU makes global income comparable.
4. Batcher & Merkle Root Generator (Off-Chain)
For blockchain efficiency, SRU batches are aggregated into a Merkle structure.
Responsibilities
group SRUs by cycle
hash leaves
build Merkle tree
produce Merkle root
prepare batch metadata
This root is submitted to Base chain.
5. Proof Registry (On-Chain, Base)
The Proof Registry stores:
cycle ID
merkle root
total SRU
timestamp
batch metadata
This ensures immutability, verifiability, and public auditability.
The Registry never stores raw earnings — only cryptographic commitments.
6. Yield Vault (On-Chain, Base)
The Yield Vault is the economic engine that:
reads totalSRU from Proof Registry
computes daily RDR emissions
distributes rewards to stakers proportionally
It uses Ridera’s dynamic emission model:
dailyEmission = min( BASE_EMISSION + (totalSRU × SRU_Emission_Factor), MAX_EMISSION )
Yield is fully backed by real-world work, not arbitrary APR.
7. Staking System (On-Chain)
Users stake RDR to earn yield generated by mobility productivity worldwide.
Staking Features
non-custodial staking
proportional reward sharing
no artificial multipliers
transparent accounting
Stakers receive rewards only when real SRU is produced.
🔐 Trust Boundary Overview
Off-Chain
Oracle
SRU Engine
Batcher
These components are responsible for correctness and verification.
On-Chain
Proof Registry
Yield Vault
Staking
These components enforce transparency and reward distribution.
On-chain contracts cannot be manipulated; they only consume verified data.
📌 Why This Architecture Works
Scalable: Can support millions of global submissions
Transparent: Proofs stored publicly on Base
Secure: Fraud-resistant multi-layer verification
Fair: Global standardization via SRU
Efficient: Minimal on-chain storage through Merkle batching
Economically sound: RDR emissions backed by real productivity
📄 Continue Reading
Next section: SRU Engine
Document Version
v1.0 — Architecture Overview
Last updated