-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
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
Render ENS Name Fix #52
Comments
What needs to be done here? |
Yea, just saw the |
The issue needs to be diagnosed and resolved. I'll eventually attempt to diagnose but its not a top priority for me personally at the moment. |
Could it be this?, Looks like an RPC error |
Found it. |
/assign |
@pavlovcik The time limit for this bounty is on Wed, 26 Apr 2023 12:03:43 GMT It looks like you haven't set your wallet address, |
/wallet ubq.eth |
Updated the wallet address for @pavlovcik successfully! Your new address: |
I just realized that we should create endpoint(s) that can substitute as a provider in case there is no injected provider. Right now I can't render ENS without a web3 enabled browser! 😔 I guess we should make a new repository to host serverlessly? |
I think we can just use another reliable ens api |
My pull request is already finished lol I just forked their API. |
[ CLAIM 37.5 DAI ]
|
renderEnsName relies on some random person's Cloudflare function which appears to be down. We should make our own solution. I hope that we can handle this entirely from the front-end?
We should also make all of our requests non blocking in case they fail!
Originally posted by @pavlovcik in #42 (comment)
The text was updated successfully, but these errors were encountered: