Sherwood ORA Dashboard

A planning and control center for a future merchant POS/scanner network powered by Sherwood Proof-of-Scan. Pilot/off-chain/simulated first, with hardware feasibility gated before any live infrastructure.

Planning Control Center
Schemas, guardrails, and simulation knobs for a future merchant POS/scanner + Proof-of-Scan system.
Pilot Workspace
Off-chain-first posture. Sample/simulated data only. Built to fail closed by default.
Ops / Research Dashboard
Device-linked scan capture, anomaly review, and receipt/POS correlation research (no payments scope).

Scan Capture

Timestamped scan events (planning-only)

Device Identity

Bind events to scannerDeviceId

Location Binding

Bind events to merchantLocationId

Pilot / Off-chain

Local logs + backend ingestion path

Note:

Planning-only and simulation-first. No live token, no mainnet, no earnings guarantees. Local ORA status is fixture-backed/read-only (no live RPC). No wallet custody, no transactions. No payment processing and no PCI scope or readiness claims.

Next steps (docs)

Operator-facing and engineer-facing references for the current planning phase. These are strategy/spec documents and do not imply live POS, payments, token, or mainnet readiness.

  • docs/HARDWARE_ENGINEER_FEASIBILITY_PACKET.md
  • docs/POS_REPLACEMENT_STRATEGY.md
  • docs/SHERWOOD_ORA_DASHBOARD_ORA_RPC_ADAPTER_ROADMAP.md

Proof-of-Scan Measurement Records

Fixture-only sample records — no live scanner ingestion. Hash-only barcode posture.

Record Count
4
Valid V1 Records
4
Invalid Records
0
Source Mode
fixture
Sample records
posm-fixture-001
2026-05-01T10:00:00.000Z
scannerDeviceId
scanner-fixture-001
merchantLocationId
loc-fixture-001
barcodeHash
hash-fixtu…-001
scanDurationMs
140
localSequenceNumber
101
signalStrength
78
posm-fixture-002
2026-05-01T10:00:05.000Z
scannerDeviceId
scanner-fixture-001
merchantLocationId
loc-fixture-001
barcodeHash
hash-fixtu…-002
scanDurationMs
155
localSequenceNumber
102
scanConfidence
92%
posm-fixture-003
2026-05-01T11:15:00.000Z
scannerDeviceId
scanner-fixture-002
merchantLocationId
loc-fixture-002
barcodeHash
hash-fixtu…-003
scanDurationMs
110
localSequenceNumber
7
signalStrength
64
posm-fixture-004
2026-05-02T09:30:00.000Z
scannerDeviceId
scanner-fixture-003
merchantLocationId
loc-fixture-003
barcodeHash
hash-fixtu…-004
scanDurationMs
205
localSequenceNumber
301
scanConfidence
81%

Local ORA Node Status

Loading local ORA status...
⚠️ SAMPLE DATA — NOT REAL HARDWARE MEASUREMENTS

Hardware Calibration Baseline

Total Scans
25
Avg Energy/Scan
0.0760 J
Min Energy
0.0504 J
Max Energy
0.0986 J

Calibrated Projections

Conservative
0.0608 J
Base
0.0760 J
Aggressive
0.0887 J

What changes when real hardware data exists?

  • Real energy harvest per scan replaces these simulated estimates.
  • Break-even and payback period calculations will reflect actual physical capabilities.
  • Tokenomics emission models can be accurately sized against true merchant scan volume.

See HARDWARE_MEASUREMENT_PROTOCOL.md for measurement requirements.

UNCERTAINTY ANALYSIS — Illustrative planning only. Variables will change.

Sensitivity Analysis

This tool demonstrates how rapidly break-even and implied value change based on two highly volatile assumptions: unit value and scan volume.

Impact of Unit Value (Base: 150 Scans/Day)

Unit ValueDaily ValueBreak-even
$0.01$1.50100 Days
$0.05$7.5020 Days
$0.10$15.0010 Days
$0.25$37.504 Days
$0.50$75.002 Days

Assuming machine cost of $150

Impact of Scan Volume (Base: $0.05 Price)

Scans/DayDaily ValueBreak-even
50$2.5060 Days
100$5.0030 Days
150$7.5020 Days
300$15.0010 Days
500$25.006 Days

Assuming reward = 1 ORA / scan (simulated)

SIMULATION ONLY — ORA planning, no live token.
DISCLAIMER: This is a simulated planning tool. No token has been launched. Legal review is pending.

ORA Emission Planning Simulator

Total Supply (ASSUMPTION, Units)
1,000,000,000
Halving Interval
48 Months
Initial Monthly Emission (Units)
10,000,000
Months to Full Emission
120

Allocation Breakdown (SAMPLE DATA)

Merchant Reward Pool
40%
400,000,000
Ecosystem Fund
25%
250,000,000
Public/Community
15%
150,000,000
Founder Reserve
20%
200,000,000

Emission Schedule (SAMPLE PROJECTION)

MonthMonthly EmissionCumulative Emission
Month 110,000,00010,000,000
Month 210,000,00020,000,000
Month 310,000,00030,000,000
Month 410,000,00040,000,000
Month 510,000,00050,000,000
Month 610,000,00060,000,000
Month 710,000,00070,000,000
Month 810,000,00080,000,000
Month 910,000,00090,000,000
Month 1010,000,000100,000,000
Month 1110,000,000110,000,000
Month 1210,000,000120,000,000
Month 2410,000,000240,000,000
Month 3610,000,000360,000,000
Month 4810,000,000480,000,000
Month 605,000,000540,000,000
Month 725,000,000600,000,000
Month 845,000,000660,000,000
Month 965,000,000720,000,000
Month 1082,500,000750,000,000
Month 1202,500,000780,000,000
Showing first 12 months, then annual snapshots.

Founder Reserve Disclosure Placeholder

The 20% founder reserve is currently a placeholder for planning purposes. No tokens exist. If launched, the founder reserve will be subject to a vesting schedule (e.g., 48 months with a 12-month cliff).

NOT FINANCIAL OR LEGAL ADVICE. This dashboard is a simulator for a proposed hardware network.

SAMPLE PILOT DATA — no real merchant onboarding exists yet.

Pilot Operations Dashboard

Total Stores
10
Total Machines
29
Proj. Scans
498,600
Sim. ORA Units
498,600
Sim. Value (USD)
$24,930

Sample Pilot Stores

Store IDNameMachinesExp. Scans/Day
store-smpl-100Sample Store 12200
store-smpl-101Sample Store 23360
store-smpl-102Sample Store 34560
store-smpl-103Sample Store 42320
store-smpl-104Sample Store 53540
store-smpl-105Sample Store 64800
store-smpl-106Sample Store 72440
store-smpl-107Sample Store 83720
store-smpl-108Sample Store 941040
store-smpl-109Sample Store 102560

NOTE: Store names and capacities are illustrative assumptions for planning only.

Pilot Readiness

Finalize BOM and manufacturer
hardware
Develop mock scan API
software
Review token vs points model
legalWaiting for legal counsel
Define GPS data collection policy
data privacy
Select 10 pilot stores
operations
Cost Analysis (Simulated)
Total Pilot Cost:$6,350
Cost / Machine:$218.966
PILOT READINESS TRACKER

Phase 1 Launch Checklist

Tracking the critical path items required before moving from simulated models to placing the first physical hardware units in the field.

Hardware Blocked
Finalize energy harvester BOM
Required Proof
Measurement Protocol validation
Hardware Not Started
Secure 10 prototype units
Required Proof
Delivery receipt
Software In Progress
Deploy mock API ingestion endpoints
Required Proof
API Docs
Software Not Started
Device authentication flow
Required Proof
Signed payload test
Legal Blocked
Token vs Points decision
Required Proof
Counsel Memo
Legal Not Started
Pilot merchant agreement
Required Proof
Signed PDF template
Operations Not Started
Identify 3 test merchants in local area
Required Proof
Merchant List
Data Privacy Blocked
Location data (GPS) opt-in flow
Required Proof
Privacy Policy update
SAMPLE FRAUD MODEL — No raw barcodes stored. Simulated risk engine.

Fraud & Risk Engine Preview

Current Rule Config

Duplicate Window:60s
Max Rate / Hour:500
Max Vol / Day:5000
Total Flags in View
0

Recent Scan Events (Scored)

TimeDeviceBarcode HashRisk Status
04:00:00dev-smpl-3hash-imp-4Clean
03:00:00dev-smpl-3hash-imp-3Clean
02:00:00dev-smpl-3hash-imp-2Clean
01:00:00dev-smpl-3hash-imp-1Clean
00:00:00dev-smpl-3hash-imp-0Clean
23:57:51dev-smpl-2hash-rate-9Clean
23:57:52dev-smpl-2hash-rate-8Clean
23:57:53dev-smpl-2hash-rate-7Clean
23:57:54dev-smpl-2hash-rate-6Clean
23:57:55dev-smpl-2hash-rate-5Clean
23:57:56dev-smpl-2hash-rate-4Clean
23:57:57dev-smpl-2hash-rate-3Clean
23:57:58dev-smpl-2hash-rate-2Clean
23:57:59dev-smpl-2hash-rate-1Clean
23:58:00dev-smpl-2hash-rate-0Clean
Showing 15 most recent sample events
SIMULATED WALLET DISPLAY — no wallet is connected.

Wallet & Claims (Simulated + Testnet)

Available Balance (Simulated)
12,450.75 ORA
≈ $622.54 USD
Pending Unsettled Rewards
+342.10 ORA
Rewards from recent scans pending Oracle validation.
Testnet Claim (Base Sepolia Only)
scan receipt exists → authorize → estimate gas → submit → persist tx hash → pending reconciliation
0xff27...f54d
Connect your wallet to claim rewards.

Machine Ownership (Mock)

DeviceLocationLifetime Yield
dev-smpl-1Store 1 Register A4,500.20
dev-smpl-2Store 1 Register B4,200.50
dev-smpl-3Store 2 Register A3,750.05

Recent Transactions (Sample Data)

Daily Scan Reward
2026-04-28 at 19:08:46 UTC
+45.50 ORA
COMPLETED
Daily Scan Reward
2026-04-27 at 20:08:46 UTC
+50.20 ORA
COMPLETED
Withdrawal
2026-04-26 at 20:08:46 UTC
-500.00 ORA
COMPLETED
Daily Scan Reward
2026-04-25 at 20:08:46 UTC
+42.10 ORA
COMPLETED

Illustrative Value Simulator (Planning)

Hardware & Usage Inputs

Reward Model Inputs

Model Logic

  • Illustrative Value: Driven strictly by `Scans × Reward per Scan × Unit Value`.
  • Harvested Energy: Driven by `Scans × Energy per Scan × Efficiency`.
  • Note: This simulator is planning-only and does not represent real earnings, token value, or merchant profitability.

Projections

Monthly Scans

15,000

500 per day

Harvested Energy

180.00 W

6000.0 mW per day

Monthly ORA Units

15 ORA

0.50 per day

Monthly Value (USD, Assumption)

$75.00

$2.50 per day

Scenario Analysis (Monthly Value, Assumption)

Conservative (-20%)

$60.00

Base

$75.00

Aggressive (+20%)

$90.00

Use this to stress-test assumptions. Do not treat outputs as earnings, legal conclusions, or a promise of token value.

Pilot Program Planner

Pilot Scope Assumptions

Pilot Outputs

Total Machines Deployed

40

Total Pilot Scans

2,160,000

Machine-Days Logged

3,600

Readiness Checklist

  • Hardware prototypes calibrated to measure actual energy yield
  • LitVM Testnet contracts deployed for scan validation
  • Initial merchant training & dashboard access setup
  • Data pipelines for scan vs. energy correlation established

Hardware Measurement Protocol (Phase 1)

Protocol Requirements

To move Sherwood Proof-of-Scan from a concept to a functional prototype, we must collect real-world electrical data from modified POS scanners. The parameters below define the baseline needed to calibrate the simulator and validate the energy harvesting model.

  • Scan Count & Duration: Measure the physical time taken to drag an item across the sensor.
  • Electrical Output: Record Voltage (mV) and Current (mA) generated during the swipe.
  • Hardware Efficiency: What percentage of the raw kinetic/electrical energy is successfully captured by the capacitor/battery?

Calibration Panel

Sample Data Only

Avg Energy / Scan

18.43 mJ

Raw output

Avg Efficiency

69.8%

Capture rate

Total Measured

16,585 mJ

From 900 test scans

Usable Energy

11,907.25 mJ

After efficiency loss

Feasibility Notes & Assumptions

Hardware Measurement

Actual energy output must be measured with physical hardware prototypes (piezoelectric or electromagnetic). Projections in this dashboard assume a nominal energy yield per scan. Hardware calibration is required to validate actual energy output without slowing scan speed.

Regulatory & Legal

Any future tokenization or collectible language (e.g., “Silver ORA”) is not a present claim. Legal classification, disclosures, and compliance requirements must be established by qualified counsel before any public launch.

Protocol & Verification

Sherwood Proof-of-Scan validation is in research mode. Current calculations assume simulated or testnet-only operation. Mainnet readiness, costs, and validation latency are unknown until the protocol, hardware, and security model are validated.

Disclaimer: This dashboard is a planning workspace for conceptual validation only. It does not provide real financial projections, and no token launch claims or profitability guarantees are made. No production wallet custody, private-key handling, real KYC, or GPS collection features are implemented in this application.

Project Roadmap

Phase 0

Companion Dashboard

Feasibility projections and merchant earnings simulator (Current MVP).

Phase 1

Hardware Measurement Prototype

Design energy harvesting module and measure actual electrical output per swipe.

Phase 2

Scan Validation Backend

Build scan validation backend and fraud prevention system.

Phase 3

Testnet Integration (Research)

Explore a testnet contract layer for claims and validation, and integrate with measured hardware output.

Phase 4

Merchant Pilot

Deploy machines in local mom-and-pop shops. Gather real-world scan rates.

Phase 5

Wallet / Production Hardening

Production hardening is gated by legal, hardware, security, and protocol readiness (no mainnet promises).