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
By default, Pkarr resolves the first response, which could be an outdated packet, either normally or maliciously sent by a peer trying to disrupt resolution of a given address. But in the background, more recent packets should be resolved, so after a failing HTTP request (with appropriate codes) the PubkyClient should check if the Pkarr cache has relevant updates that points to a different servers (Endpoint), and if so, retry calling that instead.
There should also be a limit for that to avoid the very.. very unlikely loop if someone keeps publishing new packets!
The text was updated successfully, but these errors were encountered:
By default, Pkarr resolves the first response, which could be an outdated packet, either normally or maliciously sent by a peer trying to disrupt resolution of a given address. But in the background, more recent packets should be resolved, so after a failing HTTP request (with appropriate codes) the PubkyClient should check if the Pkarr cache has relevant updates that points to a different servers (Endpoint), and if so, retry calling that instead.
There should also be a limit for that to avoid the very.. very unlikely loop if someone keeps publishing new packets!
The text was updated successfully, but these errors were encountered: