Renaming checkCanBeSpent to checkValidTransaction, dropping isValidTransaction
Added the isZero check from the removed method, removed the dead code from bridges
This commit prevent scanning non-EIP addresses, or more generally
prevent scanning address that generate warning for recipient (currently
the only possible warning is for non-EIP address for ETH/ETC).
If the warning-address is entered with keyboard instead of scanning, it
will still display the warning (as now), the behaviour doesnt change.
Closes#1412Closes#1406
Closes#1397
This commit introduce a new `warning` prop on Input component. `error`
prop will always takes precedence over it if present, btw.
We don't reject anymore recipient validity if address is either full
lowercase OR full uppercase, to support legacy formats: having a warning
will allow user to go to next step.
Obviously the fix is available for ETC as well.
Wording to be reviewed :)
Closes#1397
This commit introduce a new `warning` prop on Input component. `error`
prop will always takes precedence over it if present, btw.
We don't reject anymore recipient validity if address is either full
lowercase OR full uppercase, to support legacy formats: having a warning
will allow user to go to next step.
Obviously the fix is available for ETC as well.
Wording to be reviewed :)
The migration nonce is now stored in `app.json` file instead of
separate `migration.json`. It will ensure consistency between nonce
and app data, because the file is written in atomic way.
Migration handle legacy migration file and remove it properly.
The migration nonce is now stored in `app.json` file instead of
separate `migration.json`. It will ensure consistency between nonce
and app data, because the file is written in atomic way.
Migration handle legacy migration file and remove it properly.