Safe with Rabby: Redirect to explorer with wrong tx hash

[kernelwhisperer]

Description
I created a tx wrapping a native token and when clicking "View details"

it took me to bscscan instead of cow explorer:

https://bscscan.com/tx/0x78fbbbff49824420e0008de49798645c0bd9292a5d11030667fd90ed15e6b01b38ec7642a1fa02cd9d643023ee1403adc39e07d774f002cb5c838af3f852189b1b

Context: using Safe+Raby.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [1.65]'View on Safe' link navigates to 404 page (1/1 safe with WC connection) #4177
• Improve 'show token's address' feature #5505
• Explorer: no icons for a native token in some networks #6253
• ENS recipient is missing the link #6103

🔗 Related PRs

cowprotocol/cow-sdk#537 - fix(bridge): fix Across tx explorer link [merged]

👤 Suggested Assignees

• elena-zh
• shoom3301

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[elena-zh]

Duplicates #4177 ?

[kernelwhisperer]

And after executing the tx, the history looks like this:

Instead of saying filled.

The orders are not showing up on the cow explorer: https://explorer.cow.fi/bnb/address/0xaA248D5328c7D781a96D93d7D013bcF393157bB4

Even though they executed correctly:

https://bscscan.com/address/0xaa248d5328c7d781a96d93d7d013bcf393157bb4

[elena-zh]

@kernelwhisperer , let me give some context on it.

If you are connected to Safe using Rabby (I can see it on your screenshot), the app cannot detect whether it is a Safe TX or now, so that is why TXs return 404, that is why TXs are pending forever and cannot be executed.
This issue has beed discussed many times on Slack (one of examples) , and there is nothing we can do with it as it is on the wallet's side.

'Replaced' feature was implemented a bit earlier (in #4125) to stop these pending transactions in order to unblock you and allow placing orders.

As for other cases where a wrong TX hash can be displayed, there is an issue #4177 opened to address it one day...

Does it make sense to you? Can this task be closed?

Thanks.

[kernelwhisperer]

Yes, that makes sense regarding Replaced.

It's not clear to me if #4177 will also address "View details" taking you to etherscan with what it seems to be a safe tx id (0x78fbbbff49824420e0008de49798645c0bd9292a5d11030667fd90ed15e6b01b38ec7642a1fa02cd9d643023ee1403adc39e07d774f002cb5c838af3f852189b1b).

#4177 seems to be about fixing "View on Safe" taking you to Safe with a broken link.

[elena-zh]

It's not clear to me if #4177 will also address "View details" taking you to etherscan with what it seems to be a safe tx id (0x78fbbbff49824420e0008de49798645c0bd9292a5d11030667fd90ed15e6b01b38ec7642a1fa02cd9d643023ee1403adc39e07d774f002cb5c838af3f852189b1b).

#4177 seems to be about fixing "View on Safe" taking you to Safe with a broken link.

You're right, I've got confused and confused you.
That issue is a bit different,

In terms of the current link when connected to Safe+Rabby setup, might it be related to these conversations:

• https://cowservices.slack.com/archives/C0361CDG8GP/p1759748023679629
• https://cowservices.slack.com/archives/C0361CDG8GP/p1760954467332989?thread_ts=1760953814.834189&cid=C0361CDG8GP ?

AFAIU it cannot be addressed on our side... or it can?

[kernelwhisperer]

It is related to those 2 discussions. I also suspect it's a safe tx.

We might be able to detect it from our side (the txid being a safe id, not the wallet connection), or at the very least we can determine if it's a valid ethereum tx, and if it's not just don't show the "View details" button...

Not sure if it's worth the time though 😄