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

feat: update public RPCs #84

Merged
merged 2 commits into from
Feb 26, 2025
Merged

feat: update public RPCs #84

merged 2 commits into from
Feb 26, 2025

Conversation

dtbuchholz
Copy link
Collaborator

No description provided.

@dtbuchholz dtbuchholz requested a review from asutula February 25, 2025 19:16
Copy link

vercel bot commented Feb 25, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
faucet ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 25, 2025 7:19pm
portal ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 25, 2025 7:19pm

@dtbuchholz
Copy link
Collaborator Author

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.

@dtbuchholz
Copy link
Collaborator Author

@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.

Copy link
Contributor

@asutula asutula left a 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?

@asutula
Copy link
Contributor

asutula commented Feb 25, 2025

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.

Nothing else I can think of.

@dtbuchholz
Copy link
Collaborator Author

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?

@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 https://evm.recall.chain.love to be the mainnet RPC...which is a terrible UX b/c people will have to migrate—and likely, accidentally start using mainnet instead of testnet.

e.g., i'd expect us to use something like https://evm.recall.testnet.chain.love for testnet, and https://evm.recall.chain.love for mainnet. filecoin's a good example: https://filecoin.chain.love/

@dtbuchholz
Copy link
Collaborator Author

dtbuchholz commented Feb 25, 2025

sander noted we'll request chain.love to make a change and use a testnet subdomain: we can alias for now, and then after they switch, we can change values in the SDK and docs

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.

@asutula
Copy link
Contributor

asutula commented Feb 26, 2025

sander noted we'll request chain.love to make a change and use a testnet subdomain: we can alias for now, and then after they switch, we can change values in the SDK and docs

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 dtbuchholz merged commit c3bf227 into main Feb 26, 2025
4 checks passed
@dtbuchholz dtbuchholz deleted the dtb/public-rpcs branch February 26, 2025 14:06
@sanderpick
Copy link
Contributor

@dtbuchholz fyi, they have added the new URLs, but the old ones do NOT work anymore... PR here: #87

dtbuchholz pushed a commit that referenced this pull request Feb 26, 2025
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>
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

Successfully merging this pull request may close these issues.

3 participants