fix(core): Do not wait on notify_read_effects for transactions that may be reverted after the epoch ends

[jkrvivian]

Description of change

Merge an upstream fix: MystenLabs/sui@bf79606

Do not wait on notify_read_effects for transactions that may be reverted after the epoch ends.

Links to any relevant issues

#4674

Type of change

• Bug fix

Change checklist

• I have followed the contribution guidelines for this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have checked that new and existing unit tests pass locally with my changes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
apps-backend	⬜️ Ignored (Inspect)	Visit Preview		Feb 5, 2025 10:02am
apps-ui-kit	⬜️ Ignored (Inspect)	Visit Preview		Feb 5, 2025 10:02am
rebased-explorer	⬜️ Ignored (Inspect)	Visit Preview		Feb 5, 2025 10:02am
wallet-dashboard	⬜️ Ignored (Inspect)	Visit Preview		Feb 5, 2025 10:02am

[muXxer]

There was also a change in await_transaction_effects on upstream, which doesn't exist yet in our version. Is this important as well?

[jkrvivian]

There was also a change in await_transaction_effects on upstream, which doesn't exist yet in our version. Is this important as well?

The await_transaction_effects function has been separated from handle_certificates. This change was introduced in a previous PR (MystenLabs/sui#19401, included from v1.35.1), which added TransactionV2 RPC handler related to Mysticeti fastpath. I believe the consensus team will decide whether to implement the TransactionV2 changes. However, in this PR, I only apply changes that are compatible with the current codebase. 😃