Transaction Store¶
Transaction Store builds a lookup index for transactions found in accepted blocks. It lets clients retrieve transaction and block context by transaction ID without placing that query index in Chain.
Dependencies and inputs¶
Transaction Store connects to RabbitMQ, starts after Chain in the official Compose topology, and consumes accepted-block data.
Its RPC interface provides transaction lookup by ID. API gateways can expose that method when the service is running.
State and consistency¶
The selected release stores the derived index in BadgerDB. It is not the source of consensus truth and can be behind Chain while it processes blocks.
Because recent accepted blocks can be replaced by a fork, the index must keep its view consistent with accepted chain history. A transaction lookup that returns no result should not be interpreted as proof that the transaction never existed; the service may be disabled, unavailable, or catching up.
If Transaction Store is unavailable, transaction-by-ID queries fail, but Chain validation does not depend on that derived index.