saledjenic
saledjenic
New endpoint `VerifyPassword` exposed via `accounts` api.
As can be seen in this [screen](https://www.figma.com/proto/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=1042%3A303014&scaling=min-zoom&page-id=1023%3A298171&starting-point-node-id=1172%3A306624&show-proto-sidebar=1) if an old Status user is running the app for the first time (new app installation), he should be able to login in...
Corresponding `status-go` PR: - https://github.com/status-im/status-go/pull/2809 Corresponding `nim-status-go` PR: - https://github.com/status-im/nim-status-go/pull/16
Mainly because of the height of some keycard flows we have to increase the min app height so those flows do not look cut. Example for the factory reset flow...
Add tests for the router logic, validate routes for different input parameters. At this point, maybe, we can use the live test network, but later move to Foundry.
When calculating the best route the router should select which transaction depends on which one and later when sending the sending logic must obey that. The need for this is...
- [x] #14751 - [x] #14637 - [x] #14638 - [ ] #10791 - [ ] #14640 - [ ] Adapt the desktop app to the new Router changes -...
Under this issue we need to confirm the correctness and calculated values of all functions that implement `StatusTransaction` interface.
This issue depends on #14635 Apart from the things stated below, sending logic should know, based on the route, which transactions should be placed in parallel (immediately) and which of...
Within this issue we should go step by step through the router logic and confirm that it returns the appropriate routes for all different input values. Some things to check/improve:...