You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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;
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...)
The text was updated successfully, but these errors were encountered:
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;
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...)
The text was updated successfully, but these errors were encountered: