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

List more RPC providers and their capabilities and visibility #2311

Closed
BigLep opened this issue Sep 11, 2024 · 2 comments
Closed

List more RPC providers and their capabilities and visibility #2311

BigLep opened this issue Sep 11, 2024 · 2 comments

Comments

@BigLep
Copy link
Member

BigLep commented Sep 11, 2024

Done Criteria

There is a canonical documentation for the various RPC endpoints a builder can potentially use. This documentation lists:

  • Operator (company) name
  • URLs
  • Whether they support:
    • JSON RPC (Common Node API) read operations
    • MPoolPush for sending messages that have already been signed.
    • JSON RPC (Common Node API) write operations
    • ETH RPC read operations
    • ETH RPC write operations
  • Documentation link
  • Whether endpoint is public or requires authentication/authorization
  • If auth is required, where someone goes to request access from the provider.

Why Important

Various teams are putting work into improving the RPC experience for clients by improving the software deployed by RPC servers. It should be self-service discoverable for an app-builder who they can reach out to rely on for building their app.

User/Customer

RPC user
Maintainers so they are cognizant of who is depending on their work

Notes

  1. I'm assuming we'd be updating https://docs.filecoin.io/networks/mainnet/rpcs and https://docs.filecoin.io/networks/calibration/rpcs.
  2. Idea: a table could capture this information pretty well.
  3. This is a good opportunity to do other cleanup like Remove ChainUp from RPC providers #2299
@BigLep
Copy link
Member Author

BigLep commented Sep 11, 2024

@eshon : this suggestion came out of discussion in FilOz when @jennijuju, myself, and others from FilOz were thinking about the documentation-related work we'd ideally want accompanying the RPC improvements the team is making. Let us know if:

  1. this seems reasonable
  2. is potentially something fil-pronto can handle
  3. it's useful to talk other places (e.g., #fil-b slack, sync meeting)

Thanks!

eshon added a commit to eshon/filecoin-docs that referenced this issue Sep 24, 2024
Multi-row tables do not render well in Gitbook and single-row tables don't make sense for this info

Closes filecoin-project#2311
@BigLep
Copy link
Member Author

BigLep commented Sep 25, 2024

Handled by #2314 and #2323

@BigLep BigLep closed this as completed Sep 25, 2024
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

1 participant