Checksum validation feature | Inform users of mixed case checksum error during transaction

[adammake]

Requirements If a public key recipient in a proposed deploy has characters which have changed their casing an not longer produce a valid checksum display the following error message to the user: “The public key you provided contains mixed-case characters that don’t result in a valid checksum. Please check if the public key is correct”

Acceptance Criteria Pre-conditions: Add 'Invalid Transfer Deploy' button on the playground app Logic that is creating a valid deploy should alter any lower case letter within the target public key to a respective upper case one (i.e. c => C)

Steps to reproduce:

1. Connect with a playground app
2. Click 'Invalid Transfer Deploy' button
3. Click on 'Sign' button

Expected Result: Displaying the following error message to the user in Casper Wallet: “The public key you provided contains mixed-case characters that don’t result in a valid checksum. Please check if the public key is correct” - this error would display as designed in Figma

Implementation details:

Implement a following page:

• this view should be in the libs/layout/error folder it should be just a content page, because page layout will be customized in each app separately
• you should add error route and error page with layout in the sign transaction app
• that page will use error-content component as content section
• Available buttons on error page should be configurable using the same pattern as in the onboarding error page (using router state).
• In this scenario button should have the label Close and don't use a redirect path argument - in this case, button will close the window on click.

[piotrwitek]

@vladimir-gachkovsky your next task

[piotrwitek]

couldn't find checksum in the casper-js-sdk, and it turn out that was not implemented, changing to blocked it's implemented in the upstream depoendency

[piotrwitek]

Need to create an implementation details ticket