We need to review changes made to the 0.x branch (listed below) and cherry-pick those that make sense to the main branch.
~- [ ] addc630ef613826d3d6a90a6c4453c39aba5cfcf Release v0.1.6~
~- [ ] 33b6f64ef44335ae3d6f8fbceea3f9306ac32efc Update CHANGELOG.md~
~- [ ] 04c1c692ca06fdd78fd612a360ae6db6ccca9a05 beamer: allow request transition l1_resolved -> l1_resolved [try_to_claim]~
(this is not necessary on main since, as of very recently, we do not allow challenges once L1 resolution is done)
[x] d51e3c9ca92df20e3885494451eceb227b8a4a42 agent: Only handle ClaimMade events where agent is the claimer after processing the corresponding RequestFilled event
[x] b7f7b37c166db72866c60a50c44607a50d55ee21 agent: Only process ClaimStakeWithdrawn if all ClaimMade events have been processed
[x] 8451d84f094211ea7c90feea8af82070641115b9 fix invalidation test
~- [ ] ffc854d5799c7657cc25cebd99ca99407e3d58a5 agent: Allow challenge transition from invalidated_l1_resolved to invalidated_l1_resolved to be able to process ClaimMade events~
(this is not needed because one cannot challenge once the L1 resolution is done)
[x] 232acd039664f0e0c79e37e5b869874c6a4cccb0 agent: add invalid_fill_ids and l1_resolution_invalid_fill_ids to request
(cherry-picked into b35f22cfb7534977a978e63202a4ba0b51c70aa4; :warning: please review this one in more depth to make sure I didn't do something wrong during conflict resolution)
[x] 62b8be52188dd5e317648f622757213bffe3c924 agent: Upon claim creation check if fill id is already invalidated
[x] e3da2811c484a56cbf78a329f4759a1aa4bb17bb agent: Handle l1 resolved invalid fill ids upon claim creation
We need to review changes made to the
0.x
branch (listed below) and cherry-pick those that make sense to themain
branch. ~- [ ] addc630ef613826d3d6a90a6c4453c39aba5cfcf Release v0.1.6~~- [ ] 33b6f64ef44335ae3d6f8fbceea3f9306ac32efc Update CHANGELOG.md~
~- [ ] 04c1c692ca06fdd78fd612a360ae6db6ccca9a05 beamer: allow request transition l1_resolved -> l1_resolved [try_to_claim]~ (this is not necessary on
main
since, as of very recently, we do not allow challenges once L1 resolution is done)~- [ ] c6ca177686fdc19526617cac6a685113372b69af Release v0.1.7~
~- [ ] ffc854d5799c7657cc25cebd99ca99407e3d58a5 agent: Allow challenge transition from invalidated_l1_resolved to invalidated_l1_resolved to be able to process ClaimMade events~ (this is not needed because one cannot challenge once the L1 resolution is done)
[x] 232acd039664f0e0c79e37e5b869874c6a4cccb0 agent: add invalid_fill_ids and l1_resolution_invalid_fill_ids to request (cherry-picked into b35f22cfb7534977a978e63202a4ba0b51c70aa4; :warning: please review this one in more depth to make sure I didn't do something wrong during conflict resolution)
[x] 62b8be52188dd5e317648f622757213bffe3c924 agent: Upon claim creation check if fill id is already invalidated
[x] e3da2811c484a56cbf78a329f4759a1aa4bb17bb agent: Handle l1 resolved invalid fill ids upon claim creation
~- [ ] 440b7ddffc01d16482d78ff9f18a8830670795bc Release v0.1.8~