02 / MOBILITY TELEMETRY
Every journey. Measured.
Capture mobility activity, validate its authenticity, estimate its carbon impact, and prepare a verifiable reward event.
Distance travelled
0.00km
haversine over GPS samples
Trip duration
00:00min:sec
active recording time
Average speed
0.0km/h
distance ÷ duration
GPS signal
NOT STARTED
browser geolocation
Transport mode
Metro
chosen on this screen
Vehicle
—
no private vehicle on this trip
Trust tier
—
assigned after verification
Est. emissions
—
calculated after verification
Trip map
Press START TRIP to capture your real GPS trail. The browser will ask for location permission first.
Your journey
Trip session
- Idle
- Recording
- Paused
- Completed
- Verifying
- Verified / Failed
How did you travel for this journey?
This journey is calculated as Metro. Your saved vehicles don't decide it: what you actually travelled in does.
Testnet demo run
Not real travel. Pick how you "travelled" above, and a synthetic trip of 1 km or more runs in seconds on a ×40 clock, verifies itself, and can then be recorded on Portal V3 from your own wallet. The transaction is real; the trip is not. Rewardable modes only (EV, metro, e-bus, walking or cycling).
Checking whether this server allows testnet demo trips… Turning it on is a deliberate, server-side step: see docs/DEPLOYMENT.md.
Data source
Location is requested only after you press START TRIP and approve the browser prompt.
Trip summary
Trip summary
Capture a trip, then press STOP TRIP. The metrics are frozen into a summary and the verification action unlocks.
Verify trip
Trip authenticity engine
Four independent checks evaluate the submitted mobility record.
- PENDING
CHECK 1
Vehicle profile check
SOURCE: Your vehicle profile
Self-declared on Screen 01 · no registry is contacted
Vehicle type, fuel and mileage match your profile. Skipped for metro, bus and walking.
NOT RUN YET
- PENDING
CHECK 2
EV maker ride-log check
SOURCE: EV manufacturer API
Not integrated · deterministic mock
Ride-log availability, identity consistency, reported distance.
NOT RUN YET
- PENDING
CHECK 3
Motion & GPS validation
SOURCE: Trip telemetry
Local rules over frontend state
Sample completeness, movement, distance plausibility, replay.
NOT RUN YET
- PENDING
CHECK 4
Route validation
SOURCE: Route geometry
Local geometry · no routing API integrated
Route consistency, start/end coordinates, distance, anomalies.
NOT RUN YET
Trip evidence
Trust tier
No trust level assigned yet
Complete a trip and run verification. Trust is assigned only after all applicable checks have run.
The tier shows how much evidence backs this trip once every applicable check has passed. It is MissionEV's own measure, not an independently certified score.
Evidence tier (off-chain · does not scale the reward)
- GOLD100% evidence
- SILVER75% evidence
- BRONZE40% evidence
- REJECTED0% evidence
Gold: all checks incl. partner proof · Silver: no partner ride-log · Rejected: any critical failure. Tiers describe how much evidence backs a trip; they do not scale the on-chain reward, which the contract fixes.
Calculate CO₂ & reward
Carbon comparison
Appears after a trip is verified. Your journey is compared with a reference journey of the same distance on one accounting basis.
Record on-chain
Smart contract on Portal V3
- Commuter wallet
- —
- Portal network
- Portal V3 Testnet
- Chain ID
- — / 420420777
- Contract
- …
GAS · tPOT
—
Native Portal currency. You pay it to send recordCommute from your own wallet; it is not $MEV.
REWARD · $MEV
— preview only
Nothing is minted until the contract confirms the transaction.
Available after a trip is verified.
How it works: the verifier node (the contract's oracle signer) signs the trip; your wallet sends it, because the contract credits msg.sender. A DEMO result is never labelled as an on-chain transaction.
This browser tab
Trip history
Shared with the Rewards and Analytics screens. Stored in session storage with coordinates rounded to ~110 m.
No verified or failed trips yet in this session.