Verified history for collector cars. An iPhone app reads the car over OBD, AI explains its health, and each report's fingerprint is anchored on Robinhood Chain and peaq, so a buyer can check it was never edited.
Heritage B is a private-garage app for collector and performance cars. It is live on the App Store in English and Traditional Chinese, launching in Taiwan.
The problem: a car's condition and service history is easy to fake. Odometers get rolled back, fault codes get cleared before a sale, PDFs get edited. Buyers of high-value cars can't trust what they're shown.
How it works:
1. A Bluetooth OBD dongle streams live data (36+ parameters) to the iPhone app, which identifies the car by VIN.
2. The app builds a health report: fault codes, cleared-code tamper signals, odometer cross-checks across ECU modules. An AI concierge explains it in plain language.
3. When the owner seals a report, our backend canonicalizes it, hashes it (keccak256) and anchors the hash in the Attestations contract, now on Robinhood Chain and peaq in parallel. Raw telemetry never leaves our servers; only 32-byte hashes go on-chain.
4. Anyone can verify by VIN on the public page. The same hash on two independent chains is proof the history wasn't rewritten.
Why Robinhood Chain: cars are real-world assets. A verified, tamper-evident history is the data layer that financing, insurance and resale of tokenized vehicles will need.
Since Sep 14: chain-agnostic EVM adapter + Robinhood Chain presets in our attestor lib; multi-chain anchoring (anchorReportMulti); Foundry config for Robinhood Chain. Deployed and verified VehicleRegistry + Attestations on Robinhood Chain mainnet and testnet (same addresses as on peaq) and smoke-tested register/anchor/verify. Shipped a multi-chain verify-by-VIN page (GitHub Pages). Our production backend now seals each report on Robinhood Chain mainnet and peaq in parallel; one chain failing never blocks the other.
Bootstrapped so far; raising a pre-seed round now.
