Create entirely separate process for status update #39
Labels
enhancement
New feature or request
reliability and performance
Tasks which relate to reliability of harvester and frontend
We are adding a feature which sets a flag (should the record in the index be constantly updated or has the still-alive contract reached a point where there is no longer any interaction)
This needs to be a separate process because weaving this into the main indexing means that the main indexing is not flexible enough for all contracts (restricted to that particular contracts variable names etc.)
The reality is that this task can be done using Javascript or Python and can run on a separate lightweight system.
For the giveaway contracts the logic would be something like this
The text was updated successfully, but these errors were encountered: