If miner replaces publish deal message, it does not update that in its deal state

[whyrusleeping]

If a miner publishes a deal, but then does an mpool replace on that message before it lands (to increase the gas limit, or something) the cid recorded in their markets state store for the deal does not get updated. This leads to clients never really finding out that their data has made it into a deal, and leads to a lot of faults in estuary (estuary will mark the deal as failed on its end because it has no way of knowing that it actually landed on chain).

We can work around this by just waiting for the miner to update the deal ID in their deal status response, but this requires a good deal of extra logic to validate that everything is correct.

[whyrusleeping]

Still getting this:

2021-09-29T09:30:56.147Z        ERROR   estuary estuary/replication.go:379      failed to ensure replication of content 9123628: failed to check deal id: could not find published deal on chain: checking for message execution during lookback: found message with equal nonce as the one we are looking for (F:bafy2bzaced5e2s5awfhhgxgeisr66r47oruoowal34sydrp32dtduylk4hxiw n 18732, TS: bafy2bzaced5e2s5awfhhgxgeisr66r47oruoowal34sydrp32dtduylk4hxiw n18732)

[jennijuju]

Might be worth looking into how sealing pipeline/fsm is handling getting replaced message and follow a similar logic.