chore(immutable-x): Add console.logs for debugging issues during starkex gen #2596
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.
Summary
Added logging to debug Stark key generation and message signing issues, particularly focusing on UTF-8 encoding of messages. This is for alpha release only and contains no sensitive information.
Detail and impact of the change
Changed
signRaw
function to usetoUtf8Bytes
for message signingImxSigner
imxWallet
metaMaskWrapper
Anything else worth calling out?
This PR should help identify the root cause of the Stark signature verification failures by providing visibility into the message encoding and signing process. The logging is intended for alpha testing only and will be removed before any production release.