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
currently, on both RubiconV2 and RubiconV2_Optimism we are not tracking the transaction that caused the offer to be cancelled. for now, it probably makes the most since just to record the transaction regardless of whether it was a take, cancel, or min order sell cancel on the offer. this removes some level of insight into the cause of the cancel, but solves our immediate needs today. this will be an update to the Offer entity, and will occur any place we are updating the removed_timestamp.
The text was updated successfully, but these errors were encountered:
currently, on both
RubiconV2
andRubiconV2_Optimism
we are not tracking thetransaction
that caused the offer to be cancelled. for now, it probably makes the most since just to record thetransaction
regardless of whether it was atake
,cancel
, ormin order sell cancel
on the offer. this removes some level of insight into the cause of the cancel, but solves our immediate needs today. this will be an update to theOffer
entity, and will occur any place we are updating theremoved_timestamp
.The text was updated successfully, but these errors were encountered: