Gulf of Finland · live AIS · Robinhood Chain

Some of these ships
stop answering.

Every mark is a real hull reporting right now. The ringed ones have gone quiet. We count what they are carrying and publish the number on chain, against the stock token it moves.

01 · the signal

A ship that goes dark is a barrel nobody counted.

The hulls moving sanctioned crude out of the Baltic do not appear in any official statistic. They switch off, they meet at sea, they arrive somewhere with a shallower draught than they left with. None of that reaches the inventory reports the oil market trades on.

Radar sees them anyway. We count the tonnage, convert it to barrels, and publish the figure the day it is measured. It is a supply signal that exists nowhere else, and on this chain it is written straight against the token people hold.

Calls settled

4

Mean absolute error

320 bps

Tokens covered

7 of 194

TSLA

Q2 deliveries, Texas-built

a settled call, start to finish

+89 bps

error

We said
141,200 cars
Street said
133,500 cars
Company reported
139,950 cars
Published ahead by
27 days

Tesla Q2 2026 production and deliveries release

02 · the loop

Three steps, and the middle one is the product.

01

Count

Radar contacts with no transponder behind them. Draught marks on a laden hull. Cars draining out of a finished-vehicle lot. Public imagery, a measured area, and a method you can argue with.

02

Publish

The number, the token it describes and a hash of the evidence go on chain the day the measurement is taken. Not the imagery, just the commitment. This is the part nobody else does.

03

Settle

Weeks later the official figure lands. Anyone can resolve the reading against it, and the error in basis points sits next to the call forever.

03 · the reason it is on chain

Anyone can claim a hit rate. Almost nobody can prove one.

Alternative data is sold on a track record, and the track record is always a PDF. Nothing stops a vendor writing the history once the outcome is known, which is why desks discount the category and why an unknown provider never gets a first meeting.

A reading published on chain carries a timestamp its author does not control. The number is fixed before the answer exists. Because the stock tokens live on the same chain, a reading is keyed straight to the token’s own contract address, and a protocol pricing that token can read our figure in the same transaction.

GroundTruthOracle

chain 4663
Network
Robinhood Chain
Asset
the stock token address
Metric
keccak256 of the metric name
Value
int256, fixed point
Observed at
last pass behind the number
Published at
block timestamp
Settles with
resolve(id, actual, source)
0xe90780eE4c9ee2d7ddd05f8e29c1Cd528abb282D

04 · provenance

Every input is public, and free.

No private feed, no licensed terminal, nothing you cannot check yourself. That matters: a reading is only worth arguing with if the reader can go back to the same source.