More complete RPC provider instructions #1665
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
martinvol
requested review from
gastonponti and
ezdac
and removed request for
a team
❌ Deploy Preview for celo-docs failed.
|
ezdac
approved these changes
Feb 17, 2025
|
|
||
| After Celo mainnet transitions to L1, validators that are elegible, registered and elected must run PRC nodes in order to be elegible for rewards. | ||
| After Celo mainnet transitions to Celo L2, validators that are registered and elected can continue to receive rewards by running PRC nodes. These steps outline how validators can publish the URL of their RPC node in order to be eligible for rewards. To reduce the risk of slashing, these steps should be followed before the L2 upgrade. |
There was a problem hiding this comment.
Suggested change
| After Celo mainnet transitions to Celo L2, validators that are registered and elected can continue to receive rewards by running PRC nodes. These steps outline how validators can publish the URL of their RPC node in order to be eligible for rewards. To reduce the risk of slashing, these steps should be followed before the L2 upgrade. | |
| After Celo mainnet transitions to Celo L2, validators that are registered and elected can continue to receive rewards by running RPC nodes. These steps outline how validators can publish the URL of their RPC node in order to be eligible for rewards. To reduce the risk of slashing, these steps should be followed before the L2 upgrade. |
|
|
||
| To register as a RPC provider, a public https url needs to be registered on-chain. To do this, we will register the rpc url in a signed metadata file in the Celo Account. | ||
| To register as a RPC provider, a public https url needs to be registered on-chain. To do this, we will register the rpc url in a signed metadata file that's used to share additional information about Celo accounts. |
There was a problem hiding this comment.
Suggested change
| To register as a RPC provider, a public https url needs to be registered on-chain. To do this, we will register the rpc url in a signed metadata file that's used to share additional information about Celo accounts. | |
| To register as a RPC provider, a public HTTPS URL needs to be registered on-chain. To do this, we will register the RPC URL in a signed metadata file that's used to share additional information about Celo accounts. | |
| The metadata file has to be made available publicly and the URL where this file is hosted has to be registered on-chain as well. |
|
@martinvol there's been more changes to https://docs.celo.org/cel2/operators/community-rpc-node since this PR was created. Any change here that should be salvaged, or shall I close? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.