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
After the successful mock of the Claim Publisher (#479), the code needs to be implemented to correctly execute the service.
The validity of the functionality needs to be checked against the Rust service, who needs to correctly publish the Claim on the chain.
✔️ Solution
The Claim Publisher needs to be called at the end of every epoch, after the validator has run. It needs to correctly identify if there's a new claim, get the information from the repository, model it in the way the Rust service expects and put it on Redis.
After that, it will wait until it's called again at the end of the next epoch.
📚 Context
After the successful mock of the Claim Publisher (#479), the code needs to be implemented to correctly execute the service.
The validity of the functionality needs to be checked against the Rust service, who needs to correctly publish the Claim on the chain.
✔️ Solution
The Claim Publisher needs to be called at the end of every epoch, after the validator has run. It needs to correctly identify if there's a new claim, get the information from the repository, model it in the way the Rust service expects and put it on Redis.
After that, it will wait until it's called again at the end of the next epoch.
📈 Subtasks
The text was updated successfully, but these errors were encountered: