[DCR]: The application uses too much CPU after setting gap limit

[dmigwi]

(Issue originally authored by: @Kennedy Izuegbu in gitlab.com)

[dmigwi]

This issue is unresolved due to some limitations:

• I have tried to find a way to recover the birthday block, but currently there is no way to find the wallet's birthday block, if we can find the wallet's birthday block, we can significantly reduce the number of blocks to discover the address.

• I have tried to find a way to split the block intervals that need to address discovery to reduce CPU usage, but currently the address discovery function does not support So this issue will not be solved at the moment

  By Justin Do on 2022-11-21T09:34:31 (imported from GitLab)

(Comment originally authored by: @Kennedy Izuegbu in gitlab.com)

[dmigwi]

changed title from The application uses too much CPU after setting gap limit to {+[DCR]: +}The application uses too much CPU after setting gap limit

By Kennedy Izuegbu on 2022-11-24T10:10:07 (imported from GitLab)

(Comment originally authored by: @Kennedy Izuegbu in gitlab.com)

[dmigwi]

assigned to @justindo

By Justin Do on 2022-11-16T14:29:40 (imported from GitLab)

(Comment originally authored by: @Kennedy Izuegbu in gitlab.com)

[dmigwi]

unassigned @justindo

By Justin Do on 2022-11-21T09:47:17 (imported from GitLab)

(Comment originally authored by: @Kennedy Izuegbu in gitlab.com)