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
Base-58 service only supports the case when the user knows the location of missing characters.
A new option is needed for when that location is not known. But the option has to work with any number of missing characters without needing to hard-code each case individually.
The text was updated successfully, but these errors were encountered:
73e8596 solves this for a special case (compressed key missing 3 chars).
We can add more code for a couple more small cases (3 missing is already 4 billion keys to check).
8d13be8 solves this for special case (both compressed and uncompressed keys missing 2 chars) which closes this issue.
We can add the case for >= 4 chars missing but the number of keys to check grows fast and the colde also becomes very slow 2.9k -> 4.2 mil -> 4.0 bil -> 2.8 tril -> 1.5 quad.
I prefer postponing any additional work on this to after code including SHA got more optimized (eg. using SIMD) and GPU support is added.
Base-58 service only supports the case when the user knows the location of missing characters.
A new option is needed for when that location is not known. But the option has to work with any number of missing characters without needing to hard-code each case individually.
The text was updated successfully, but these errors were encountered: