You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your feature request?
Right now, the GetBlockRange method streams blocks from lowest height to tallest height. For BlazeSync, it might be useful to have the blocks streamed backwards - i.e., tallest height to lowest height. Maybe have an optional parameter that specifies the direction in which to stream blocks
How would this feature help you?
Streaming blocks backwards allows wallets to detect incoming spends quicker, allowing users access to their most recent transactions first.
This should be easy, just generalize GetBlockRange() to run the loop index either up or down. Rather than adding an optional parameter, it may make sense to just allow start=20, end=10 to mean return 20, 19, ... 10. Currently, those arguments would return an empty list. This approach is almost backward-compatible -- close enough, I think.
What is your feature request?
Right now, the
GetBlockRange
method streams blocks from lowest height to tallest height. For BlazeSync, it might be useful to have the blocks streamed backwards - i.e., tallest height to lowest height. Maybe have an optional parameter that specifies the direction in which to stream blocksHow would this feature help you?
Streaming blocks backwards allows wallets to detect incoming spends quicker, allowing users access to their most recent transactions first.
cc: @LarryRuane , @braddmiller
The text was updated successfully, but these errors were encountered: