When calling `SendTransaction` sometimes the value would be a string
(most cases), sometimes the value would instead big a `BigInt`, which
would be serialized to an integer, and status-go would be unable to
parse it as it expects values to be a string.
This commit makes sure that values are always serialized as string
before sending them over.
Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
Previously we used both "keycard" and "hardwallet" names for stuff
related to keycard. It can be confusing as "hardwallet" might be used
for other hardwallets in future.
Prior to this commit `sign-message-completed` effect would always use
the `wrong-password` label for error handling. We now ensure that `wrong-password`
is only used in case the error in question has a code `5`, which is
associated to unmatching passwords.
In any other case we'll use the `message` attached to the `error`.
Fixes#8275
Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
This commit ensures that a user can flawlessly interact with a keycard,
regardless of the moment when the card was tapped to the device. To make
it so:
- in case if the card was tapped before the interaction the user doesn't
need to re-connect card to continue
- in case if the connection with the card was lost during the interaction
the application restarts that interaction as soon as the card was
connected again (unless the user canceled the flow)
This commit allows setting waku-mode and waku-bloom-filter-mode
dynamically.
It requires a relogin for the changes to take effect.
Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>
Remove screens that are not needed for new flow
Replace keycard flows with new interaction
If card connected start processing on sheet open
Remove outdated pin screens
Signed-off-by: Gheorghe Pinzaru <feross95@gmail.com>
Do not hide sheet when tag was lost during generating keys
Change cancel action for no-key on card recovery
Change pin screen when loading keys to an initialised card
Signed-off-by: Gheorghe Pinzaru <feross95@gmail.com>
Currently we have two ways to restore a multiaccount:
- by entering a mnemonic phrase
- by pairing a keycard with an existing multiaccount
In both cases, when we detect that a user tries to recover an existing
multiaccount we interrupt recovering and propose them to unlock that
multiaccount instead.
fix#8702
- use ethereum.utils sha3 function to hash passwords before sending them
to status-go
- some native calls take password as one of their params: they now take
hashed-password (still a string, only relevant for status-react caller)
- some native calls take password within a map of rpc params: it now
needs to be hashed with `ethereum.core/sha3`
Signed-off-by: yenda <eric@status.im>
Andrea Maria Piana
andrey
Roman Volosovskyi
Gheorghe Pinzaru
yenda
Richard Ramos
Michael Bradley, Jr
Vitaliy Vlasov
Pascal Precht
Dmitry Novotochinov