We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From my current understanding of the client URI resolution process, there is an infinite loop if using a URI Resolve Wrapper
Lets say you have an "ens-resolver.eth" URI resolver wrapper Invoking a URI "test.eth" would work like this:
client.invoke("test.eth") resolveUri client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"] forEach URI resolver wrapper client.invoke("ens-resolver.eth") resolveUri client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"] forEach URI resolver wrapper client.invoke("ens-resolver.eth") resolveUri client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"]
This is still just a theory and needs to be tested. If there is indeed an infinite loop, we can address it as a separate issue.
The text was updated successfully, but these errors were encountered:
More details on possible solution: https://hackmd.io/CJjkN8OzSv-3vEBPzOwQBQ
Sorry, something went wrong.
nerfZael
Successfully merging a pull request may close this issue.
From my current understanding of the client URI resolution process, there is an infinite loop if using a URI Resolve Wrapper
Lets say you have an "ens-resolver.eth" URI resolver wrapper
Invoking a URI "test.eth" would work like this:
client.invoke("test.eth")
resolveUri
client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"]
forEach URI resolver wrapper
client.invoke("ens-resolver.eth")
resolveUri
client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"]
forEach URI resolver wrapper
client.invoke("ens-resolver.eth")
resolveUri
client.getImplementations("uri-resolver") -> returns ["ens-resolver.eth"]
This is still just a theory and needs to be tested. If there is indeed an infinite loop, we can address it as a separate issue.
The text was updated successfully, but these errors were encountered: