-
Notifications
You must be signed in to change notification settings - Fork 2
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
Community and Networks sections #67
Conversation
f22be07
to
5819ee1
Compare
5819ee1
to
da8b6b1
Compare
780aa7d
to
433ba2b
Compare
4136a87
to
9897049
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finished review.
728b81d
to
7998621
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Nice to see the Network section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff. One comment on formatting nit, but approving anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My comments are suggested improvements, and therefore non-blocking.
|
||
## High Volume Notice | ||
|
||
Running a node that will have a high volume of transactions or queries from one or more servers requires altering the defaults. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be useful to give some parameters for what you mean by "high volume" instead of or in addition to saying "high volume"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It depends on so many things, I'm not sure how to quantify it. Open to ideas.
|
||
## Local Instant Sealing | ||
|
||
Used for local development. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... only?
Co-authored-by: Shannon Wells <shannonwells@users.noreply.github.com>
4c83e85
to
d152c48
Compare
@@ -0,0 +1,140 @@ | |||
# Running a Collator | |||
|
|||
Collator Node operators will need to meet technical and financial requirements to serve as a candidate to be chosen to form the next block. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that the technical requirements are outlined below. However, there doesn’t appear to be any additional information regarding the financial requirements. Could you please provide more details on that?
@@ -0,0 +1,29 @@ | |||
# Collator Decentralization Roadmap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
@@ -18,7 +18,7 @@ Each node also runs a copy of the current Relay Chain Runtime WASM, for coordina | |||
|
|||
Like many blockchains, there are multiple deployments of Frequency. | |||
The production system, referred to as Mainnet, uses the validators of the production Polkadot Relay Chain. | |||
A separate system for testing and development known as Testnet uses validators on the Polkadot Rococo Testnet Relay Chain. | |||
A separate system for testing and development known as Testnet uses validators on the Paseo Relay Chain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a good place to link to PolkadotJS app for each one.
New Sections:
Updated some markdown inconsistencies