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

add page on block proposal #8446

Merged
merged 14 commits into from
Dec 13, 2022
Merged

add page on block proposal #8446

merged 14 commits into from
Dec 13, 2022

Conversation

jmcook1186
Copy link
Contributor

Description

adds new page to consensus-mechanisms/pos describing the process of proposing a block, including validator selection, block creation and propagation and block rewards. Part of the "post-merge gaps" epic.

Related Issue

#8285

@jmcook1186 jmcook1186 mentioned this pull request Nov 2, 2022
9 tasks
@gatsby-cloud
Copy link

gatsby-cloud bot commented Nov 2, 2022

✅ ethereum-org-website-dev deploy preview ready

Copy link
Contributor

@minimalsm minimalsm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't get through all of this but looking good so far 👍

@@ -0,0 +1,71 @@
---
title: Block proposal
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

src/content/developers/docs/consensus-mechanisms/pos/block-proposal/

Thoughts on the location of this page? Other than complexity, I feel like this being a subpage of blocks makes sense. Not cut-and-dry, would love opinions here.

cc: @wackerow @samajammin

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could see it going in either place honestly. I think given the complexity and prereq's that include PoS, I would opt to just keep it here under consensus-mechanisms/pos

@@ -0,0 +1,71 @@
---
title: Block proposal
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could see it going in either place honestly. I think given the complexity and prereq's that include PoS, I would opt to just keep it here under consensus-mechanisms/pos

@minimalsm minimalsm merged commit 36f5460 into dev Dec 13, 2022
@minimalsm minimalsm deleted the jc-block-production branch December 13, 2022 14:03
@corwintines corwintines mentioned this pull request Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content 🖋️ This involves copy additions or edits
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants