search

connext / monorepo

Connext is a modular stack for trust-minimized, generalized communication between blockchains.
https://docs.connext.network
MIT License
284 stars 163 forks source link

[ICE: 4] Wrong origin address displayed on Transfers page #5980

Open par94 opened 3 months ago

par94 commented 3 months ago

Describe the bug On transfers page (https://connextscan.io/transfers) origin address displayed is an address of the Connext contract, not the senders

Link to ticket in discord

To Reproduce Steps to reproduce the behavior:

  1. Go to (https://connextscan.io/transfers)
  2. Origin address displayed is an address of the Connext contract, not the senders

Screenshots

Screenshot 2024-04-03 at 14 23 44 Screenshot 2024-04-03 at 14 26 22 Screenshot 2024-04-03 at 14 25 51 Screenshot 2024-04-03 at 14 25 43 Screenshot 2024-04-03 at 14 25 23 Screenshot 2024-04-03 at 14 24 33

@oncall

just-a-node commented 3 months ago

It's a known thing - that's the Multisend contract. We need the same kind of tx.origin fix for this but it hasn't been prioritized.

ekbainova commented 2 months ago

Not only original, but also direction address is displayed incorrect. The destination address is usually wrong when bridging ETH (it indicates as the destination the address of the unwrapper) https://lineascan.build/address/0x5a53576dde5071719a9a3a9e78e68cbcdf863253 Example tx: https://connextscan.io/tx/0x955029f2109e6293d0f6167c3a344fa2fe89b932cd0f4c571bbfd8c844126b46

or when using an aggregator (it indicates as the destination the address of the aggregator's receiver contract). https://basescan.org//address/0xec03b65cbdc5f8858b02f44eba54c90664249fb1 Example tx: https://connextscan.io/tx/0x071d3289ac5a6c0238dbb5dc62c347671cfc3b8f73474304a9530de4fb3bca16