Websocket service should use ContractsFetch.acsFollowingAndBoundary as transaction source, not TransactionClient#getTransactions #3880
Closed
Description
we probably don't want to consume all transactions from the very beginning all the time.
We want to address the other interpretation of this (not the one @lima-da originally made), in that the WebSocketService should not use the full transaction stream, but instead the concatenation of ACS and transactions-since-ACS-end, which we've implemented as the Akka graph component ContractsFetch.acsFollowingAndBoundary.
Making offset a visible concept (or not) is outside the scope of this issue; please direct to #3878.
This is a prerequisite to #3878.