My idea is that most users don't know an exact block height they should rescan from, but they likely know something such as "I didn't receive any transactions before one month ago" or something like that. Most users will not know how to convert back and forth between a date+time and a block height.
So we could offer two options in the "Rescan" area:
The current option, which is an arbitrary block height
OR a dropdown of relative times, such as:
The last day
The last week
The last month
The last year
We could have each of the two options selectable via a radio button, so only one input would be active at a time.
If a relative time is chosen, SD will calculate the block height by using our average block time plus a safety factor, such as 10%.
My idea is that most users don't know an exact block height they should rescan from, but they likely know something such as "I didn't receive any transactions before one month ago" or something like that. Most users will not know how to convert back and forth between a date+time and a block height.
So we could offer two options in the "Rescan" area:
* The current option, which is an arbitrary block height
* OR a dropdown of relative times, such as:
* The last day
* The last week
* The last month
* The last year
We could have each of the two options selectable via a radio button, so only one input would be active at a time.
If a relative time is chosen, SD will calculate the block height by using our average block time plus a safety factor, such as 10%.
My idea is that most users don't know an exact block height they should rescan from, but they likely know something such as "I didn't receive any transactions before one month ago" or something like that. Most users will not know how to convert back and forth between a date+time and a block height.
So we could offer two options in the "Rescan" area:
We could have each of the two options selectable via a radio button, so only one input would be active at a time.
If a relative time is chosen, SD will calculate the block height by using our average block time plus a safety factor, such as 10%.