You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mempool's transaction and batch graphs are currently somewhat indirectly coupled.
As an example, transaction expiration is currently tracked separately in the mempool but ideally transaction and batch graphs should determine their expirations internally (see comment).
One hurdle is that the batch graph is effectively an overlay on top of the transaction graph. Which means separating them is difficult. One possible angle is to increase the richness of the graph return values, which could help the mempool react to changes in one that should impact the other.
The text was updated successfully, but these errors were encountered:
The mempool's transaction and batch graphs are currently somewhat indirectly coupled.
As an example, transaction expiration is currently tracked separately in the mempool but ideally transaction and batch graphs should determine their expirations internally (see comment).
One hurdle is that the batch graph is effectively an overlay on top of the transaction graph. Which means separating them is difficult. One possible angle is to increase the richness of the graph return values, which could help the mempool react to changes in one that should impact the other.
The text was updated successfully, but these errors were encountered: