Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction history misinformation #5458

Open
Ade-kola opened this issue Nov 16, 2023 · 0 comments
Open

Transaction history misinformation #5458

Ade-kola opened this issue Nov 16, 2023 · 0 comments

Comments

@Ade-kola
Copy link

Expected behavior

When an account perform a cross-chain transaction (LSK) to another account on a different chain (Sidechain), the liskmainchain account of the receiver should not have the transaction information/history of the said transaction.

A chain. should hold transaction information that was defined for the chain.

Actual behavior

When a cross-chain transaction is been performed, Lisk mainchain of the recipient holds the transaction history instead of the defined chain. However, the defined chain received the transaction (token), but doesn't receive the transaction log. See image below;

Screenshot 2023-11-16 at 14 44 38 Screenshot 2023-11-16 at 14 55 04

Steps to reproduce

Initiate a cross chain transaction from a mainchain to a sidechain, check the wallet details of the recipient account on the main and sidechain, looking out for the transaction hsitory.

Which version(s) does this affect? (Environment, OS, etc...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants