Closed fredo closed 2 years ago
This bug was now fixed by a different strategy. Namely only processing requests after both chains have synced. This led to the fact that we will definitely get the fill event before the claimMade event and will not call try_to_claim again
This was a bug happening on startup. Currently the agent only jumps into the
claimed
state directly after calling the claim transaction. That is fine as long as the agent is running. But on start up the agent potentially will have called the claim transaction for a request already. Theclaimed
state represents the state where the agent claimed the request (because he is the filler). We should also jump into that state whenever we receive aCLaimMade
event where the agent is the claimer.