SRU Engine
Standardized Revenue Unit (SRU) Generation System
Global Mobility Income → Unified On-Chain Value
🚀 Introduction
The SRU Engine is one of the core components of the Ridera Protocol. It transforms real-world mobility earnings—sent by riders, couriers, and fleet operators—into a single, comparable, standardized metric called SRU (Standardized Revenue Unit).
SRU allows Ridera to normalize global earnings across:
195+ countries
multiple mobility platforms
various work categories
different currencies
economic patterns and cost-of-living differences
It ensures fair representation of real-world work and provides a unified basis for on-chain yield distribution.
🎯 Purpose of the SRU Engine
The SRU Engine solves critical problems in global mobility income:
Huge variation in earnings across countries
Different payout structures across platforms
Irregular work patterns (full-time, part-time, peak-only)
Currency and purchasing power differences
High volatility in bonus structures
SRU standardizes all of this into a universal measurement, enabling transparent and fair yield distribution.
🧱 SRU Engine Workflow
The SRU Engine receives only verified data from the Oracle. No unverified earnings can ever enter SRU computation.
🔷 1. Inputs to the SRU Engine
The SRU Engine receives structured data:
Earnings Data
total payout
base fare
bonuses
surge income
tips
platform metadata
Economic Metadata
worker region
currency
mobility platform
worker category
timestamp (cycle period)
Oracle Verification Flags
validated = true
no-duplicate
no-anomaly
trust-score adjustment
Only validated earnings are processed.
🔷 2. Weighting System
SRU computation relies on a three-layer weighting model that ensures fair global normalization.
2.1 Country / Region Weight
Accounts for:
cost of living
average delivery/ride income
regional economic strength
purchasing power
Example (illustrative):
2.2 Platform Weight
Each platform has different payout structures.
2.3 Work Category Weight
Based on work intensity:
All weights are dynamic and updated as the ecosystem grows.
🔷 3. SRU Formula
The SRU Engine applies the following formula:
Properties:
Region-normalized
Platform-consistent
Fair for all worker types
Resistant to manipulation
SRU is always proportional to real earnings, but adjusted for global fairness.
🔷 4. Daily Cycle Creation (Batching)
The SRU Engine groups all computed SRUs into a 24-hour cycle:
Each cycle includes:
total SRU
individual SRU per user
platform breakdown
region metadata
timestamp
Merkle root
Cycles ensure consistent, predictable yield periods.
🔷 5. Merkle Root Generation (For Proof Registry)
The SRU Engine sends batch data to the Batcher:
All SRUs hashed
Merkle tree constructed
Merkle root created
Root + metadata sent on-chain
The Proof Registry stores:
cycleId
merkleRoot
totalSRU
timestamp
This ensures transparency and auditability.
🔷 6. Output of the SRU Engine
The final outputs are:
Per-user SRU
Used for:
contribution weighting
worker analytics
future reputation score system
Total SRU (Cycle Level)
This is the number used by the Yield Vault to calculate daily RDR emissions.
Merkle Root
Used for proof verification on-chain.
🔥 Why SRU Makes Ridera Unique
SRU enables Ridera to:
✔ Tokenize human productivity
✔ Create globally fair yield
✔ Normalize global earnings into a single metric
✔ Maintain transparency and immutability
✔ Support decentralized workforce identity
✔ Enable future credit systems based on work
SRU is the world’s first universal on-chain measure of mobility work.
📄 Next Section
Continue to Oracle Design to understand how earnings are validated before SRU computation.
Document Version
v1.0 — SRU Engine
Last updated