Skip to content
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

bug: sepolia rpc from viem is down (our viem ver is old) #169

Open
1 task done
portdeveloper opened this issue Jan 21, 2025 · 2 comments
Open
1 task done

bug: sepolia rpc from viem is down (our viem ver is old) #169

portdeveloper opened this issue Jan 21, 2025 · 2 comments

Comments

@portdeveloper
Copy link
Member

Is there an existing issue for this?

Current Behavior

https://status.sepolia.org/

Image

Expected Behavior

It should work!

Steps To Reproduce

  1. go to abi.ninja
  2. select sepolia from the dropdown
  3. search for address 0xaEF9A3c02A69646b7dB8A183E4B1274d77e2393F
  4. wait for decompilation to finish (it takes a long time and prints an error to the console)

Anything else?

I think we should up rainbowkit + wagmi + viem

@technophile-04
Copy link
Member

Ohh yes noticed it but didn't knew the reason, thanks @portdeveloper for digging it!

Btw why don't we use the getAlcemyHttpUrl util from networks.ts here, instead of passing the public rpc URL to heimdall?

rpcUrl: publicClient?.chain.rpcUrls.default.http[0],


we should up rainbowkit + wagmi + viem

Yup let's do it any which ways 🙌

@portdeveloper
Copy link
Member Author

Thanks for the feedback @technophile-04 , and also that is a great question!

The reason why I didnot use the getAlcemyHttpUrl util from networks.ts is that it is limited in the number of chains it supports!
viem/chains has a lot of chains and if we use the rpcUrl from those, we basically get decompilation work for all the chains in viem/chains compared to what we can get with getAlchemyHttpUrl util

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants