Colony vs Bitcoin
Reading from a Qubic node …
Colony pulse
Mining solutions per tick, live from the tick stream. Each one is a network that beat its parent; the node logs whether it was accepted and how many errors it made over the year-long frame.
Hour by hour
Each cell is one hour: ▲ closed level or higher than the hour before (in whole USDT), ▼ lower. Pale: the last hours of the year-long frame the epoch started with. Bright: hours stored live during this epoch — the ones the colony could not know in advance. Dashed: the hour still to come.
Record
Every live hour this server has recorded, one week per epoch (one row per day, one column per hour of the day, UTC). A node only answers for the running epoch, so the record starts with this server's first reading — earlier hours are not filled in afterwards.
Hit rate
How often the colony's call matched the hour, against 50 % for a coin toss. It appears once calls can be read; a call counts only if it was fixed before its hour arrived.
Overview
How Bitcoin moved and how the colony called it, by hour, day, epoch or month.
About this page
Since epoch 240 Qubic's mining is graded on the real direction of Bitcoin: every hour the nodes store the BTC/USDT price on-chain through Qubic's Price oracle, and the ant colony searches for networks whose output matches up and down. Here is every hour as it arrives.
Directions only, no prices: the prices come from Binance via Qubic's Price oracle, and this report does not republish exchange data. Times in your local time zone. Not investment advice — a research experiment of the Qubic network.