• Data from the BEEFY commitment: ValidatorAddresses, SignedCommitment (we can generate the Payload from this)
• Data from the initial verification tx: on-contract commitment ID (we can use this to query Payload from contract)
• Data from the second verification tx: on-contract commitment ID (and therefore Payload)

In live mode we're doing these lookups using hashes from txs we send, but in sync mode in order to associate a BEEFY commitment with an initial verification tx we need to compare the Payload because we don't have any other information available. We could adopt the contract's commitment ID and use it to refer to BEEFY commitments in the relayer database, but even then we'd need to compare the Payload to make the initial association.

Maybe in sync mode we could subscribe to our own address' sent transactions so that they're available to make these lookups? Open to ideas on this one.

Originally posted by @denalimarsh in #384 (comment)