Skip to content

Fix cross-chain In/Out tag always showing "In" on multichain instances - #3624

Merged
tom2drum merged 1 commit into
mainfrom
tom2drum/issue-3608
Aug 10, 2026
Merged

Fix cross-chain In/Out tag always showing "In" on multichain instances#3624
tom2drum merged 1 commit into
mainfrom
tom2drum/issue-3608

Conversation

@tom2drum

Copy link
Copy Markdown
Collaborator

Description

Resolves #3608

On multichain instances the cross-chain In/Out tag always showed In, because direction required config.chain.id to match the source chain — and that id is unset when there is no single current chain.

Direction is now derived only from whether the page address is the sender and/or recipient. Adds a Self tag when both sides are the page address. Shared logic lives in CrossChainFromToTagTx and is used by the cross-chain transfers and messages list/table rows.

Environment variables

None

Minimum API version

None

Breaking or incompatible changes

None

Additional information

None

Made with Cursor

- Construct the tag only based on recipient or/and sender hash.
- Introduce the "Self" variant for the tag
@tom2drum tom2drum added the bug Something isn't working label Aug 10, 2026
@tom2drum
tom2drum merged commit 4911a20 into main Aug 10, 2026
12 checks passed
@tom2drum
tom2drum deleted the tom2drum/issue-3608 branch August 10, 2026 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cross-chain In/Out tag is always "In" on multichain instances

1 participant