-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: update public RPCs #84
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
note: the only remaining API that directly hits our nodes is the faucet URL. i dont think there's a way around doing this due to how the faucet works—just calling it out. |
@asutula is there anything else we want to include in a release? considering we want ppl to use our public RPCs asap, i'll publish a new release after i merge this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, but I'm a bit surprised about the URLs considering this is a testnet. What will the chain.love URLs look like for mainnet? Maybe I'm missing something about how they differentiate between testnet and mainnet?
Nothing else I can think of. |
@asutula hm, yeah these feel like mainnet RPCs; it's what we set up with them tho: https://recall.chain.love. once we go to mainnet, i'm guessing we'd want e.g., i'd expect us to use something like |
sander noted we'll request chain.love to make a change and use a so i think we're good to publish these changes now—mainly because we have ETHDenver hackathons starting tomorrow, and the load balancing etc with chain.love will be useful. |
I don't know what "alias" means in this context, but I believe you and @sanderpick. Cool! |
@dtbuchholz fyi, they have added the new URLs, but the old ones do NOT work anymore... PR here: #87 |
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @recallnet/chains@0.0.3 ### Patch Changes - Updated dependencies \[[`c3bf227`](c3bf227)]: - @recallnet/network-constants@0.0.3 ## @recallnet/network-constants@0.0.3 ### Patch Changes - [#84](#84) [`c3bf227`](c3bf227) Thanks [@dtbuchholz](https://github.com/dtbuchholz)! - update to use public RPCs from protofire / chain.love ## @recallnet/sdk@0.0.4 ### Patch Changes - Updated dependencies \[[`c3bf227`](c3bf227)]: - @recallnet/network-constants@0.0.3 - @recallnet/chains@0.0.3 - @recallnet/contracts@0.0.1 Co-authored-by: textileio-machine <40302381+textileio-machine@users.noreply.github.com>
No description provided.