Conversation
766b6b5 to
db326e1
Compare
6b49c8d to
4e80f7c
Compare
db326e1 to
acb7eb8
Compare
|
Some thoughts about the scanning info screen topic:
|
That's possible, but I think that's contradictory with 3rd point, more on that below.
Definitely
Ok now that's important. I think there are 2 choices here:
The "scan just that period" feature is a bit tricky, but I think it's necessary for people to find out a payment they know they received, otherwise that's a bit of a bummer if they haven't opened the app for a while. Worst case is that we will waste scanning work by rescanning blocks we already scanned when doing the "normal" catch up. I've been thinking about that and I think we can mitigate that by keeping the user defined scan ranges in storage (no need for a db for that) and when doing the "normal" scan we read that in storage and skip blocks that we already scanned. The lastScan logic stays inchanged. It's a bit of work, but I think it's not that bad either. [1] Actually we may allow multiple blindbit instances, it would help scanning reliability in case one of the blindbit is offline/slow on network, and it would also boost the trust since we don't seem to rely on a central backend anymore. |
acb7eb8 to
3302bbc
Compare
69ec7ea to
0e738b5
Compare
3302bbc to
ee6c7b3
Compare
0e738b5 to
157b323
Compare
…Transaction` Add `confirmation_blockhash` to `RecordedTransaction` types Rename `confirmedAt` to `confirmationHeight` in Dart
ee6c7b3 to
9f1c951
Compare
157b323 to
ff17a01
Compare
d147463 to
a87a3f8
Compare
64a0ab1 to
6a769d5
Compare
fd1bfa3 to
0f37eb7
Compare
a1bf52d to
ed4f586
Compare
669c815 to
4e9f112
Compare
This address #187
When scanning, user can tap on the scan progress bar and open a new screen that display the following information:
screenshots