Introduction
The Transaction Tracker is a system-level native blueprint that records the outcome of every transaction intent the network commits, filed under its intent hash and expiry epoch. The system reads it before executing a transaction, which is how the network refuses to run the same intent twice.
What it records
Every transaction submitted to Radix carries an intent hash, a commitment to the manifest and its header, including the epoch range in which the transaction is valid. The Transaction Tracker is the ledger's record of which intent hashes have already been used, and with what outcome. Its status type has three values: CommittedSuccess, CommittedFailure and Cancelled.
Before executing a transaction, the system looks its intent hash up in the tracker and rejects the transaction if the hash is already there, with IntentHashPreviouslyCommitted whether the first attempt succeeded or failed, or IntentHashPreviouslyCancelled. A wallet can therefore resubmit a transaction it never saw confirmed without the risk of it running twice.
This makes the life of an intent a small finite state machine: once an intent is recorded as committed, it cannot be committed again, and the tracker is the part of the ledger that enforces it.
A ring of partitions
Storing every intent hash forever would grow without bound, so the tracker is a fixed-size ring. Its package definition reserves every substate partition from just above the main base partition up to 255, and assigns each one a window of EPOCHS_PER_PARTITION = 100 consecutive epochs. A transaction's record is filed in the partition covering its expiry epoch, computed by partition_for_expiry_epoch; an expiry outside the ring's current window has nowhere to go and the transaction is not accepted.
When a commit takes the ledger 100 epochs past the window's start, the system calls advance: the start epoch moves forward one window, the start partition steps on by one and wraps around at the end of the range, and the partition it leaves, which holds the oldest records, is deleted. Records age out by being overwritten rather than deleted individually, so the cost of the whole structure is bounded and constant.
The repository's own calculate_coverage test pins the size of that window: at the network's targeted five-minute epoch, the ring covers 65 days. The same test asserts the covered range is at least the transaction validator's max_epoch_range, 8,640 epochs or 30 days: that is the design constraint, and it runs in CI. How long a transaction may stay valid before it expires is not an independent parameter; it is bounded by how much history the tracker can hold.
System-owned, not user-callable
The tracker is a native blueprint but not an ordinary one. Its create function is gated behind system_execution(SystemExecution::Protocol), so only the protocol itself may instantiate it: there is exactly one tracker, created at genesis, and no blueprint or badge can make another. Writes into it come from the system layer as it commits each transaction, in update_transaction_tracker, not from a method call a manifest can make.
Its substate is versioned (TransactionTrackerSubstateV1) and stores only the ring's parameters: start epoch, start partition, the partition range, and the epochs-per-partition figure: so the layout can change in a future protocol update without a migration of the records themselves.
