Consider using spatial matcher for merging `INCOMING_COULD_MATCH` cases

Description

There is a set of merging rules that can be summarized as ‘can't merge an incoming send with incoming receive, at least until we prove the receive doesn't match the send', or ‘the pink “If we can prove they don't match” cells in Mike’s  sheet’.

They correspond to cases dubbed INCOMING_COULD_MATCH in MultiParentCasperMergeSpec.
As mentioned in https://github.com/rchain/rchain/pull/2606#discussion_r306715323, this would require having actual data and continuations (not just their hashses) in the event log we're processing.

The currently agreed on way for having the 'rich event log' is the 'report replay'. Having to do a replay kind of defeats the purpose of merging though.

The goal of this ticket is to reconsider our options here and come to a common understanding on their feasibility and steps forward.

Status

Assignee

Unassigned

Reporter

Artur Gajowy

Components

None

Story Points

None

Epic Link

None

Labels

Priority

Medium
Configure