Consider including counts of assertions/retractions in the TxReport #281

New issue

Open

opened 2020-08-06 16:57:48 +00:00 by gburd · 0 comments

gburd commented

2020-08-06 16:57:48 +00:00

(Migrated from github.com)

In our current explorations of syncing, it's useful to know if a TxReport represents a transaction that did nothing. Currently the only way to do find this out is by querying a transactions table after the fact. A simple way to represent this state would be with a simple flag on the TxReport - but perhaps we'd want to know more information about what a transaction did at some point - hence the counts.

This assumes that we'll be using transactor for syncing purposes beyond initial prototyping.

In our current explorations of syncing, it's useful to know if a TxReport represents a transaction that did nothing. Currently the only way to do find this out is by querying a `transactions` table after the fact. A simple way to represent this state would be with a simple flag on the TxReport - but perhaps we'd want to know more information about what a transaction did at some point - hence the counts. This assumes that we'll be using transactor for syncing purposes beyond initial prototyping.