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

expand light node section (wiki migration) #6223

Merged
merged 2 commits into from
May 5, 2022
Merged

expand light node section (wiki migration) #6223

merged 2 commits into from
May 5, 2022

Conversation

jmcook1186
Copy link
Contributor

Description

This PR adds information to the light node section of /developers/docs/nodes-and-clients/index.md.

This is part of the wiki migration. I initially expected that this might have to be a page in its own right or at least a new, expanded section in the existing landing page. However, on reflection the wiki information is execution layer specific (in fact, Geth specific), dated to 2018 and light clients have not really taken off on Ethereum yet anyway - they are something exciting for the near future. For these reasons I decided the intended outcome (overview of light clients) is best served by linking to Geth's LES protocol docs and maintaining just a short, forward looking description in the existing light nodes section on the landing page.

Related Issue

#5690

@gatsby-cloud
Copy link

gatsby-cloud bot commented May 5, 2022

Gatsby Cloud Build Report

ethereum-org-website-dev

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 17m

Performance

Lighthouse report

Metric Score
Performance 🔶 24
Accessibility 💚 100
Best Practices 💚 100
SEO 💚 92

🔗 View full report

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.

Looks great! Some tiny suggestions below.

For a future page/iteration we don't really explain gossip protocols here or anywhere on the website. Could be useful given the excitement around using gossip for statelessness.

src/content/developers/docs/nodes-and-clients/index.md Outdated Show resolved Hide resolved
src/content/developers/docs/nodes-and-clients/index.md Outdated Show resolved Hide resolved
src/content/developers/docs/nodes-and-clients/index.md Outdated Show resolved Hide resolved
src/content/developers/docs/nodes-and-clients/index.md Outdated Show resolved Hide resolved
src/content/developers/docs/nodes-and-clients/index.md Outdated Show resolved Hide resolved
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.

@jmcook1186 merged my suggestions to pull this in, feel free to undo them in a separate PR if you disagree strongly with any of them.

@minimalsm minimalsm merged commit 97e2559 into ethereum:dev May 5, 2022

The execution client Geth includes a [light sync](https://github.com/ethereum/devp2p/blob/master/caps/les.md) option. However, a light Geth node relies upon full nodes serving light node data. Few full nodes opt to serve light node data, meaning light nodes often fail to find peers. There are currently no production-ready light clients on the consensus layer; however, several are in development.

There are also potential routes to providing light client data over the [gossip network](https://www.ethportal.net/. This is advantageous because the gossip network could support a network of light nodes without requiring full nodes to serve requests.
Copy link
Member

Choose a reason for hiding this comment

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

Link syntax broken here... will patch

@wackerow wackerow mentioned this pull request May 5, 2022
@minimalsm minimalsm mentioned this pull request May 9, 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