FRY fork transactions appear as unmatched Send & Receive
acknowledged
Eric
What is the issue?
Transactions from the FRY fork appear as separate send and receive events that are not linked into a single bridge event.
Who is affected?
Users interacting with transactions from the FRY fork.
What is the workaround?
Users may manually edit transactions to reflect their on-chain activity.
⚠️ Manual Edit Disclaimer
Manual edits are a temporary workaround and will
not
be overwritten by future fixes or re-syncs. However, manual changes can sometimes result in duplicate transactions or other unintended side effects. For this reason, edits should be made with caution. Once a permanent fix is released, manually edited transactions may need to be reviewed or removed to ensure accuracy.Keywords: fry fork, bridge transactions, unmatched events, transaction tracking
Log In
Support Ops Tools
marked this post as
acknowledged