The road to 16 million state operations per second.
TrackBTC turns Bitcoin history into operational intelligence. We built our state engine in Rust to carry balances, relationships, and behavior forward together—so every movement arrives with the history that gives it meaning.
State had to become usable while the operation was still hot.
1.429 billion source transactions.
A full-history workload used to construct durable current, temporal, and relationship state.
16.0 million operations per second.
History and relationship state built at the speed required for temporal analysis, velocity, acceleration, behavioral change, and graph traversal.
The dense modern tail averaged 3.64 million state-building operations per second with just 6.1% variation. State is the product. Predictable speed is what makes it infrastructure.
Every movement has a history.
A large transfer carries several questions with it. Is this a familiar counterparty? Does the timing fit the wallet group’s history? Is the holder accumulating, distributing, or moving value within its own infrastructure?
Answering those questions takes current state, chronology, and relationships together. A balance tells you where value sits. Its history shows how it got there. The surrounding activity puts the movement in context.
TrackBTC builds that context as it processes the chain. Operational reports, monthly reports, and Month in Motion draw on the resulting state to show movements, counterparties, and changes in behavior over time.
The movement is the event. The surrounding state is the intelligence.
Each view starts from state the engine has already built.
The workload defined the engine.
Our starting point was the operation itself. Blocks, transactions, value, identity, relationships, temporal boundaries, replacements, and snapshots form the operating model. We made those concepts native to the engine.
Operations become current, temporal, and relationship state within the same system. Progress commits at explicit boundaries. Recovery resumes from verified state. Readers share a coherent foundation for their own questions.
That design carries the meaning of each operation forward while the data is still hot. As history grows, the state grows with it.
History makes a familiar pattern—and a departure from it—visible.
See the operation around the transaction.
TrackBTC connects the largest deposits and movements with the wallet groups and counterparties involved. It preserves activity over time, showing recurring relationships, changes in movement patterns, and shifts between accumulation and distribution.
Operational reports put recent activity in focus. Monthly reports establish the longer view. Month in Motion follows the developing month. Together, they give institutions a record of their own activity and their peers’ behavior.
For treasury and security teams, that context supports a practical question: does this movement fit the operation we understand? The evidence includes what changed, what persisted, and the history behind both.
The State Transition Engine is the product.
An ordered operation enters. The engine applies the domain transition, materializes the resulting state, carries chronology and relationships forward, and commits recoverable progress. Readers start from truth that already exists.
Measured across the full history.
The engine reached a peak of nearly 16 million internal state-building operations per second. These operations construct the history and relationship state behind temporal analysis, velocity, acceleration, behavioral change, and graph traversal.
The complete production rebuild covered 1.429 billion source transactions. Across 14 full-sized work units in the dense modern tail, the mean was 3.64 million state-building operations per second, with a 6.1% coefficient of variation.
Rust gave us direct control over memory and concurrency, with explicit handling of invalid state across billions of operations. That control supports both throughput and predictable progress as the workload becomes denser.
The result is usable state at the scale of the history it represents.
A production foundation for state evolution.
The engine delivers forward state materialization, temporal memory, relationship state, and verified recovery in production. The next architectural step is a reversible state runtime: retained versions, reverse application, replay, and branching state.
- 01Accept ordered operations
- 02Apply native transitions
- 03Carry chronology forward
- 04Commit verified progress
- 05Expose usable state
- 01Retain transition sets
- 02Create atomic versions
- 03Move backward or forward
- 04Branch alternate state
- 05Reproduce any moment
The pattern extends beyond Bitcoin.
Trading engines turn orders into books, positions, and risk. Payment systems turn instructions into balances and settlement. Event-sourced CQRS systems turn commands into authoritative projections. Simulations and digital twins branch possible worlds. State machines coordinate long-running work. Agent control planes turn millions of actions into shared operational reality.
These systems share a need: ordered operations must produce coherent state while preserving chronology, invariants, and recovery. Bitcoin gives us a demanding production workload for that pattern.
That is the category: STE—State Transition Engine. TrackBTC demonstrates state materialization at production scale. A reversible, versioned runtime is the direction we are developing from that foundation.
And once state evolution can be reproduced precisely, operational history becomes something else too: machine-learnable experience.
Read how state becomes AI training dataEvery operation adds to the intelligence.
State evolution is the product.
Built in Rust and proven across 1.429 billion transactions. The engine carries history, relationships, and behavioral change into the operational intelligence TrackBTC delivers today.
Discuss state infrastructure TrackBTC throughput figures come from a completed production rebuild on 10 September 2026. The 15.996M figure, rounded to 16.0M, is a peak internal state-building rate, not transaction throughput or report response time.