Open
Conversation
…et address Unfortunately, as currently written, the two following expression: bech32ToBytes(X_CHAIN_ADDRESS) and bech32ToBytes(P_CHAIN_ADDRESS) intra-account results in the same output. The generated UTxO will include a pseudo-CorETH address which will prevent import on the C-chain and return the following error: Error: import tx transfer failed verification: wrong signature: expected signature from JTWYVMiL9CmJvWBVbhZzMtyV8wW4C1Ztt but got from auLWN59QX8b9hFwt1e5oLaCRWMM1j4HU
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current example to export from P-to-C are incorrect and will result in an UTxO which is going to fail RPC node submission check on import.