Measurement System Overview

How Measurement Validation Works in O Blockchain

🔍 Complete Validation Workflow

The O Blockchain uses a multi-layered validation system to ensure data accuracy and prevent fraud. Here's the complete process from invitation to reward.

📬 Step 1: Invitation

Invite Creation:

System → Selects qualified user → Creates invite
Invite contains:
  - invite_id (unique, cryptographically secure)
  - invited_user (CPubKey of specific user)
  - type (WATER_PRICE or EXCHANGE_RATE)
  - currency_code (e.g., "USD", "EUR")
  - expiration (14 days from creation)

User Receives:

"You've been invited to measure WATER_PRICE for USD"

You can choose:
  Option 1: Online measurement (10.00 O reward)
  Option 2: Offline measurement (100.00 O reward)

User Decision: At this point, the user decides whether to submit online or offline measurement.

📊 Step 2: Measurement Submission

Option A: ONLINE Measurement

User submits:
  - measurement_id (unique)
  - submitter (their public key)
  - currency_code ("USD")
  - price (100 cents)
  - volume (33.8)
  - volume_unit ("fl oz")
  - source_url ("walmart.com/water-bottles")
  - source: USER_ONLINE
  - invite_id (from invitation)

Option B: OFFLINE Measurement

User submits:
  - measurement_id (unique)
  - submitter (their public key)
  - currency_code ("USD")
  - price (100 cents)
  - volume (33.8)
  - volume_unit ("fl oz")
  - location ("40.7128°N, 74.0060°W")
  - proof_image_hash ("QmXxxx...") // IPFS hash
  - source: USER_OFFLINE
  - invite_id (from invitation)

✅ Step 3: Automated Validation (Immediate)

When a measurement is submitted, the system automatically validates it:

3.1 Security Checks:

1. Invite ID exists? ✅
2. Invite not expired? ✅
3. Invite not already used? ✅
4. Submitter matches invited user? ✅ (CRITICAL SECURITY CHECK)

3.2 Volume Validation:

5. Volume unit valid? (e.g., "L", "fl oz") ✅
6. Volume in acceptable range?
   - Metric: 0.9L - 1.1L ✅
   - Imperial: 30 fl oz - 37 fl oz ✅
7. Price positive? ✅
8. Calculate price per liter (pro-rated) ✅
9. Price per liter reasonable? (1 cent - 10M cents) ✅

3.3 Source-Specific Validation:

For ONLINE (USER_ONLINE or BOT_ONLINE):

10. URL provided? ✅
11. URL format valid? ✅
12. URL accessible? ✅

For OFFLINE (USER_OFFLINE or BOT_OFFLINE):

10. Photo hash provided? ✅
11. Location provided? ✅
12. Location format valid? (GPS coordinates) ✅
13. Timestamp within 60 minutes? ✅ (photo must be recent)

3.4 Gaussian Range Validation:

14. Get recent measurements for same currency
15. Calculate mean and standard deviation
16. Check if new value is within acceptable range (±3σ)
17. Record deviation for confidence scoring

Result:

If ALL checks pass → Measurement accepted for human validation
If ANY check fails → Measurement REJECTED immediately

👥 Step 4: Human Validation (Peer Review)

After automated validation, the measurement needs human validators to confirm accuracy.

4.1 Validation Invitation:

System → Selects random validators → Sends validation invites
Invite contains:
  - measurement_id (to validate)
  - type (ONLINE_VALIDATION or OFFLINE_VALIDATION)
  - reward amount (10.00 O or 80.00 O)

4.2 Online Validation (10.00 O Reward):

Validator's Task:

1. Visit the URL provided
2. Verify water price on website
3. Verify volume/container size
4. Verify unit matches
5. Confirm price matches
6. Submit validation: APPROVED or REJECTED

What Validator Checks:

✅ URL actually shows water for sale
✅ Price matches what submitter claimed
✅ Volume matches (e.g., 1.0L, 33.8 fl oz)
✅ Unit is correct
✅ Currency is correct

4.3 Offline Validation (80.00 O Reward):

Validator's Task:

1. Review photo provided (IPFS hash)
2. Physically travel to location (if possible)
3. Verify photo is real and recent
4. Confirm price tag visible in photo
5. Confirm volume label visible
6. Confirm unit visible
7. Submit validation: APPROVED or REJECTED

What Validator Checks:

✅ Photo is authentic (not stock image or photoshopped)
✅ Price tag clearly visible
✅ Volume clearly visible on label (e.g., "33.8 FL OZ")
✅ Unit clearly visible
✅ Photo appears recent (not old/faded)
✅ Location plausible (optional: physically verify)

4.4 Validation Threshold:

Minimum validators required: 3 (Config::MIN_VALIDATORS_REQUIRED)

Example progression:
  0 validators: Not validated (0% confidence)
  1 validator:  Not validated (10% confidence)
  2 validators: Not validated (20% confidence)
  3 validators: VALIDATED ✅ (30% confidence)
  5 validators: VALIDATED ✅ (50% confidence)
  10+ validators: VALIDATED ✅ (100% confidence)

4.5 Consensus:

if (validators.size() >= MIN_VALIDATORS_REQUIRED) {
    measurement.is_validated = true;
    measurement.confidence_score = min(1.0, validators.size() / 10.0);
}

💰 Step 5: Reward Distribution

Once a measurement is validated, rewards are created during block mining.

Measurement Submitter Reward:

Online measurement: 10.00 O (quick, convenient)
Offline measurement: 100.00 O (requires travel, more effort)

Validator Rewards:

Online validation: 10.00 O per validator (remote check)
Offline validation: 80.00 O per validator (requires verification effort)

Total Rewards Example:

Scenario: Offline water price measurement with 3 validators

Submitter (offline): 100.00 O
Validator 1 (offline): 80.00 O
Validator 2 (offline): 80.00 O
Validator 3 (offline): 80.00 O
─────────────────────────────
Total: 340.00 O created

All coins created during block mining (no pre-existing funds)

🔄 Complete Flow Diagram

┌─────────────────────────────────────────────────────────────┐
│ STEP 1: INVITATION                                          │
├─────────────────────────────────────────────────────────────┤
│ System → Selects User → Sends Invite                       │
│ Invite: "Measure WATER_PRICE for USD"                      │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│ STEP 2: USER CHOOSES METHOD                                 │
├─────────────────────────────────────────────────────────────┤
│ Option 1: Online (10.00 O)  │  Option 2: Offline (100.00 O)│
│ - Find URL                   │  - Go to store              │
│ - Note price + volume        │  - Take photo               │
│ - Submit URL                 │  - Get GPS location         │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│ STEP 3: AUTOMATED VALIDATION (Immediate)                    │
├─────────────────────────────────────────────────────────────┤
│ ✅ Security: Submitter matches invite?                      │
│ ✅ Volume: In range (0.9-1.1L or 30-37 fl oz)?             │
│ ✅ Unit: Valid ("L", "fl oz", etc.)?                        │
│ ✅ Price: Positive and reasonable?                          │
│ ✅ Gaussian: Within statistical range?                      │
│ ✅ Source: URL accessible OR photo + location valid?        │
│ ✅ Timestamp: Within 60 min (offline only)?                 │
│                                                             │
│ Result: PASS → Continue | FAIL → Reject Immediately        │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│ STEP 4: HUMAN VALIDATION (Peer Review)                      │
├─────────────────────────────────────────────────────────────┤
│ System → Selects 3+ Validators → Sends Validation Invites  │
│                                                             │
│ ONLINE Validator (10.00 O):        OFFLINE Validator (80.00 O):│
│ - Visits URL                       - Reviews photo          │
│ - Confirms price                   - Confirms authenticity  │
│ - Confirms volume/unit             - Confirms price visible │
│ - Submits: APPROVED ✅             - Confirms volume visible│
│                                    - (Optional: visits location)│
│                                    - Submits: APPROVED ✅   │
│                                                             │
│ Threshold: 3 validators required → Measurement VALIDATED    │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│ STEP 5: REWARD DISTRIBUTION (Block Mining)                  │
├─────────────────────────────────────────────────────────────┤
│ Block is mined → Coinbase transaction created:             │
│                                                             │
│ [Mining Reward: 50.00 O]                                   │
│ [Measurement Reward: 100.00 O → Submitter]                 │
│ [Validation Reward 1: 80.00 O → Validator 1]               │
│ [Validation Reward 2: 80.00 O → Validator 2]               │
│ [Validation Reward 3: 80.00 O → Validator 3]               │
│ [Stabilization Coins: Variable → Stable currency users]    │
│                                                             │
│ Total new coins: 390.00 O + mining + stabilization         │
└─────────────────────────────────────────────────────────────┘
                            ↓
┌─────────────────────────────────────────────────────────────┐
│ STEP 6: DATA USAGE                                          │
├─────────────────────────────────────────────────────────────┤
│ Validated measurement → Added to daily average calculation  │
│ Daily average → Used for stability monitoring               │
│ Stability status → Triggers stabilization mining if needed  │
│ Exchange rates → Used for currency exchange transactions    │
└─────────────────────────────────────────────────────────────┘

🛡️ Multi-Layer Security

Layer 1: Cryptographic Security

✅ Invite ID tied to specific user (CPubKey)
✅ Submitter must match invited user
✅ Cannot steal or trade invites

Layer 2: Automated Validation

✅ Volume range validation
✅ Gaussian range validation (statistical outlier detection)
✅ Timestamp validation (offline: must be within 60 min)
✅ URL accessibility validation (online)
✅ Location format validation (offline)

Layer 3: Human Validation

✅ Peer review by 3+ independent validators
✅ Validators check actual source (URL or photo)
✅ Confirms volume, unit, price accuracy
✅ Prevents fraud and errors

Layer 4: Reputation System

✅ Validators with higher reputation count more
✅ Bad validators lose reputation
✅ Consistently accurate validators gain reputation

📊 Validation Requirements by Type

ONLINE Measurements:

Submitter Provides:

✅ URL (e.g., "walmart.com/water-bottles")
✅ Price (e.g., 100 cents)
✅ Volume (e.g., 33.8)
✅ Unit (e.g., "fl oz")
✅ Currency code (e.g., "USD")

Validators Check:

1. Visit URL
2. Confirm water product exists
3. Confirm price matches
4. Confirm volume/unit matches
5. Vote: APPROVED or REJECTED

Automated Checks:

✅ URL accessible?
✅ URL format valid?
✅ Price in Gaussian range?
✅ Volume in acceptable range (0.9L-1.1L)?

OFFLINE Measurements:

Submitter Provides:

✅ Photo (IPFS hash, e.g., "QmXxxx...")
✅ GPS Location (e.g., "40.7128°N, 74.0060°W")
✅ Price (e.g., 100 cents)
✅ Volume (e.g., 33.8)
✅ Unit (e.g., "fl oz")
✅ Currency code (e.g., "USD")

Validators Check:

1. Review photo
2. Confirm photo shows water bottle
3. Confirm price tag visible
4. Confirm volume label visible (e.g., "33.8 FL OZ")
5. Confirm unit visible
6. Confirm photo appears recent/authentic
7. (Optional) Physically visit location to verify
8. Vote: APPROVED or REJECTED

Automated Checks:

✅ Photo hash provided?
✅ Location format valid?
✅ Timestamp within 60 minutes?
✅ Price in Gaussian range?
✅ Volume in acceptable range (0.9L-1.1L)?

🎯 Validation States

Measurement Lifecycle:

1. SUBMITTED → measurement received, automated validation pending
2. AUTO_VALIDATED → passed automated checks, needs human validators
3. PENDING_VALIDATION → waiting for 3 validators
4. PARTIALLY_VALIDATED → has 1-2 validators (not enough)
5. VALIDATED → has 3+ validators, accepted into system ✅
6. REJECTED → failed validation (automated or human)

Confidence Scoring:

confidence_score = min(1.0, validators.size() / 10.0)

Examples:
  3 validators  = 30% confidence (minimum to be validated)
  5 validators  = 50% confidence
  7 validators  = 70% confidence
  10 validators = 100% confidence (maximum)

💰 Reward Schedule

For Submitters:

Measurement Type	Reward	Effort Level
Water Price (Online)	10.00 O	Low - just find URL
Water Price (Offline)	100.00 O	High - store visit + photo
Exchange Rate (Online)	10.00 O	Low - find URL
Exchange Rate (Offline)	100.00 O	High - store visit + photo
URL Submission	20.00 O	Medium - find reliable source

For Validators:

Validation Type	Reward	Effort Level
Online Validation	10.00 O	Low - check website
Offline Validation	80.00 O	High - review photo/visit location

Why Different Rewards?

Offline requires physical travel (time, gas, effort)
Offline provides higher quality data (harder to fake)
Online is convenient but easier to manipulate
Validators doing offline checks earn more (verification effort)

🔒 Fraud Prevention

Attack: Fake URL Submission

Attacker: Submits fake walmart.com URL with wrong price
Automated: URL accessible ✅ (real site)
Validators: Visit URL → Price doesn't match → REJECT ❌
Result: Measurement rejected, attacker gets nothing

Attack: Photoshopped Image

Attacker: Submits edited photo with fake price
Automated: Photo hash valid ✅, location valid ✅
Validators: Review photo → Detect editing artifacts → REJECT ❌
Result: Measurement rejected, attacker reputation drops

Attack: Old Photo Reuse

Attacker: Submits 2-week old photo
Automated: Timestamp check → More than 60 min old → REJECT ❌
Result: Measurement rejected immediately

Attack: Invite ID Theft

Attacker: Steals someone's invite ID
Automated: Submitter != Invited User → REJECT ❌
Result: Security violation logged, measurement rejected

Attack: Extreme Outlier

Attacker: Submits $100/L for water (normal is $1/L)
Automated: Gaussian check → 50σ deviation → REJECT ❌
Result: Measurement rejected as statistical outlier

📈 Data Quality Assurance

Statistical Validation:

Every measurement is checked against:
  - Mean of recent measurements
  - Standard deviation
  - Acceptable range (±3σ typically)
  - Historical patterns

Cross-Validation:

Multiple validators must agree:
  - Prevents single validator fraud
  - Requires consensus
  - Higher confidence with more validators

Source Diversity:

Data comes from:
  - User online measurements
  - User offline measurements
  - Automated bot scraping
  - Validated URL library
  
Multiple sources → Higher reliability

🎯 Summary

Validation is Multi-Layered:

✅ Cryptographic - Invite tied to user
✅ Automated - Volume, range, timestamp, URL/location checks
✅ Human - 3+ peer validators confirm accuracy
✅ Statistical - Gaussian range prevents outliers
✅ Consensus - Multiple validators must agree

Measurements are Invite-Only:

Blockchain selects users - Users cannot submit measurements without invitation
One invite per user - Blockchain picks specific user for specific measurement
User chooses method - Once invited, user decides online or offline submission
Reward adjusts - Based on method chosen (online: 10 O, offline: 100 O)
No open submission - Cannot measure water prices without being invited by the system

Security is Robust:

Cannot steal invites (cryptographic binding)
Cannot submit fake data (validators check)
Cannot reuse old photos (timestamp check)
Cannot submit outliers (Gaussian check)

Rewards are Fair:

Higher effort = Higher reward
Validators compensated appropriately
All rewards created during mining
Transparent and predictable

🌍 Global Measurement Policy

Philosophy: Monitor Water Prices EVERYWHERE

The O Blockchain stablecoin system requires global water price data to function correctly, even in regions where cryptocurrency is banned or restricted. This section outlines our comprehensive strategy for collecting measurement data worldwide while respecting local laws and protecting users.

Core Principles:

Universal Data Collection: Water price measurements must be collected from ALL regions, regardless of legal status
User Safety First: Never expose local users to legal risk in banned regions
Legal Compliance: Respect local laws while maintaining system integrity
External Measurement: Use "outside-region" users to safely measure data in restricted areas
Reward Fairness: Compensate measurers appropriately while respecting transaction restrictions

🗺️ Region Classifications

1. ALLOWED Regions (Full Access)

Countries: Switzerland, Singapore, UAE, Portugal, Germany, Australia, Canada
Strategy: LOCAL_ONLY measurement (locals preferred)
Rewards: FULL_REWARDS (transaction-based payments)
Legal Status: Crypto-friendly, no restrictions

Policy:

✅ Local users can submit measurements
✅ External users can also submit (but locals preferred)
✅ Automated bots can collect data
✅ Full transaction rewards to all participants
✅ Invitations sent to local users
✅ No legal risk

2. MONITORED Regions (Compliance Required)

Countries: USA, UK
Strategy: MIXED measurement (local + external)
Rewards: FULL_REWARDS with KYC compliance
Legal Status: Regulated but allowed with compliance

Policy:

✅ Local users can participate (with KYC)
✅ External users welcome
✅ Automated bots can collect data
✅ Full transaction rewards (with compliance)
✅ Invitations sent to locals and external users
⚠️ KYC required for local users
✅ Low legal risk with compliance

3. BLOCKED Regions (Crypto Banned)

Countries: China, India, Bangladesh, Nepal, Bolivia, Ecuador
Strategy: EXTERNAL_ONLY measurement
Rewards: EXTERNAL_ONLY (no transactions to blocked regions)
Legal Status: Cryptocurrency banned or severely restricted

Policy:

❌ Local users CANNOT participate (legal protection)
✅ External users CAN submit measurements
✅ Automated bots can collect data
❌ NO transaction rewards to local users
✅ Full rewards to external measurers
✅ Track unpaid rewards for future claiming
❌ NO invitations to local users
✅ Invitations sent to external users
🚨 High legal risk for locals, low risk for external users

🛡️ How External Measurement Works

What is an "External" User?

An external user is someone whose home country is different from the target measurement region.

Example:

User from Switzerland measuring water prices in China = External User ✅
User from China measuring water prices in China = Local User ❌ (blocked)

Why External Users?

Legal Safety: External users (tourists, travelers, researchers) face minimal legal risk
Data Integrity: Still get accurate, on-the-ground measurements
User Protection: Locals in banned regions are protected from legal consequences
System Completeness: Ensures global coverage of water price data

Who Can Be External Measurers?

🌍 Travelers visiting blocked regions
📊 Researchers studying water markets
🏢 Business people with international operations
👥 Users from nearby allowed regions
🤖 Automated bots scraping public data

💰 Reward Distribution by Region

FULL_REWARDS (Allowed & Monitored Regions)

Measurement Submitted → Validated → Transaction Created → Coins Sent

Rewards paid immediately as blockchain transactions
Full amount as specified in reward schedule
No restrictions or delays

EXTERNAL_ONLY (Blocked Regions)

Local User: Measurement → Validated → Reward Tracked (NO transaction) → Future Claim
External User: Measurement → Validated → Transaction Created → Coins Sent ✅

Local Users: Rewards are earned and tracked but NOT paid as transactions
External Users: Receive full transaction rewards immediately
Future Claims: If region becomes allowed, tracked rewards can be claimed

Unpaid Reward Tracking

struct UnpaidReward {
    CPubKey user;           // User who earned reward
    string country_code;    // Blocked region where earned
    int64_t amount;         // Amount owed
    string reason;          // "BLOCKED_REGION_TRANSACTION"
    int64_t timestamp;      // When earned
}

Why Track Unpaid Rewards?

Fairness: Users still "earned" the reward through valid work
Future Claims: If legal status changes, rewards can be paid
Reputation: Can count toward user reputation/standing
Transparency: Clear accounting of all measurement contributions

📋 Invitation Strategy by Region

Allowed Regions:

Target: 100 measurements
Strategy: Send invites to LOCAL users (prefer natives)
Backup: If not enough locals, add external users

Monitored Regions:

Target: 100 measurements
Strategy: Send invites to BOTH local (with KYC) and external users
Mix: 70% local, 30% external for diversity

Blocked Regions:

Target: 100 measurements
Strategy: Send invites ONLY to EXTERNAL users
Selection: Prioritize nearby regions and users with travel history
NO local invites: Protect locals from legal risk

🔒 Security & Compliance

Legal Risk Mitigation:

No Local Participation in Blocked Regions: Locals are automatically excluded from invitations
Clear Warning Messages: External users are informed they're measuring a restricted region
Optional Participation: External users can decline invitations to blocked regions
Automated Bot Priority: Use bots for public data in high-risk regions

Transaction Restrictions:

No Blockchain Transactions to Blocked Regions: Prevents legal issues
Off-Chain Tracking: Rewards tracked in separate database
Reputation Credits: Local users in blocked regions earn reputation (non-monetary)
Future Claiming: Mechanism for claiming if legal status changes

Data Validation:

External measurements undergo additional validation
Cross-reference with bot data
Require photo proof for offline measurements
Higher validator count for blocked-region data

🎯 Benefits of Global Policy

For the O Blockchain:

✅ Complete global water price coverage
✅ Stabilization mechanism works in all regions
✅ Accurate exchange rate calculations worldwide
✅ Robust data even in restricted markets

For Users:

✅ Locals in blocked regions protected from legal risk
✅ External users earn rewards for helping
✅ Fair tracking of all contributions
✅ Future claim possibility if laws change

For Legal Compliance:

✅ No blockchain transactions to banned regions
✅ Respects local cryptocurrency laws
✅ Uses legal data collection methods (public info, travelers)
✅ Clear audit trail and policy documentation

For Data Quality:

✅ Multiple data sources (locals tracked, externals measured, bots scraped)
✅ Cross-validation from different perspectives
✅ Continuous monitoring even in restricted regions
✅ No data gaps in the system

📝 Technical Reference

Policy Manager: src/measurement/measurement_policy.h
Implementation: src/measurement/measurement_policy.cpp
Integration: Measurement invite system automatically applies policies
RPC Commands: Policy information available via measurement RPC

For developers: The policy is automatically enforced during invite creation and reward distribution. No manual intervention required.

The O Blockchain measurement system ensures accurate, fraud-resistant, globally comprehensive water price data for the stablecoin mechanism! 💧✅🌍

https://o.international

A Nonprofit Association Focused on the Creation of a Water Price-Based Stable Coin

Association de Loi 1901 – France Numéro de Siret (French SIREN): 924 014 467 00014