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

Problem: Missing flexible global RPC / chain selection #187

Open
ricky321q opened this issue Oct 24, 2022 · 1 comment
Open

Problem: Missing flexible global RPC / chain selection #187

ricky321q opened this issue Oct 24, 2022 · 1 comment
Assignees

Comments

@ricky321q
Copy link
Contributor

For now developers have to manually set their cronos RPC and cronos ChainId,
I purpose that we should enable plugin server of selection,
developers could choose what's the env they're using(testnet / mainnet / devnet), then we have default rpc/chainId for testnet and mainnet, they don't have to change for it. if developers choosing devnet, then we let them to input like 8545 , 3000.
So developers don't have to set for every Actors and don't have to worry about wrong RPC / ChainId.
But also need to consider like our public RPC might not be powerful enough , they might want to use their own rpc to run.
So we could let developers to choose the network first, and we have option to still let them to configure about it.

@tomtau
Copy link
Contributor

tomtau commented Oct 25, 2022

But also need to consider like our public RPC might not be powerful enough , they might want to use their own rpc to run.

Yeah, I think this is the important point; it can perhaps have a default node for testing, but it should display warnings and point developers to blockdaemon, rockx or other node providers, so that they setup dedicated full nodes for production

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

4 participants