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

Naming: how to call the RPC 2.0 product to replace current Solana RPC #3

Open
grooviegermanikus opened this issue Nov 2, 2023 · 2 comments
Labels
community question Further information is requested from anybody on community

Comments

@grooviegermanikus
Copy link
Contributor

Goal

Find a term that helps to clarify the concept during the project phase.
The described product will be the RPC implementation that will operate next to the Solana Validator instance.

@grooviegermanikus
Copy link
Contributor Author

how about Vanilla RPC 2.0
See here for definition of the terminology

@grooviegermanikus grooviegermanikus added the community question Further information is requested from anybody on community label Nov 13, 2023
@buffalojoec
Copy link

This might not be the best place to ask this, but if the RPC is going to be a decoupled sidecar implementation based entirely on geyser, couldn't a validator operator choose which RPC sidecar to run?

If so, we could just have an interface for the RPC sidecar, dub that interface something like "Solana RPC Sidecar Interface" (or much, much better than that), and just let anyone implement it. Perhaps some nodes may choose different implementations based on the hardware they run, performance benefits for down-stream users, MEV, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community question Further information is requested from anybody on community
Projects
None yet
Development

No branches or pull requests

2 participants