gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-04-25 16:58:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix md format (#8434)

Browse Source 
The merge queue is failing due to md lint changes:

https://github.com/sigp/lighthouse/actions/runs/19491272535/job/55783746002

This PR fixes the lint. I'm targeting the release branch so we can get things merged for release tomorrow, and we'll merge back down to `unstable`.


  


Co-Authored-By: Jimmy Chen <jchen.tc@gmail.com>

Co-Authored-By: Michael Sproul <michael@sigmaprime.io>
This commit is contained in:
Jimmy Chen
2025-11-19 22:00:36 +11:00
committed by GitHub
parent 02d0c6a8ce
commit 8e54f6e1a8
5 changed files with 21 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
book/src/advanced_blobs.md
View File

@@ -6,12 +6,12 @@ With the [Fusaka](https://ethereum.org/roadmap/fusaka) upgrade, the main feature
Table below summarizes the role of relevant flags in Lighthouse beacon node:
| | Post-Deneb, Pre-Fulu || Post-Fulu ||
|-------|----------|----------|-----------|----------|
| Flag | Usage | Can serve blobs? | Usage | Can serve blobs? |
| --prune-blobs false | Does not prune blobs since using the flag | Yes, for blobs since using the flag and for the past 18 days | Does not prune data columns since using the flag | No |
| --semi-supernode | - | - | Store half data columns | Yes, for blobs since using the flag for a max of 18 days |
| --supernode | - | - | Store all data columns | Yes, for blobs since using the flag for a max of 18 days |
| | Post-Deneb, Pre-Fulu | | Post-Fulu | |
|---------------------|-------------------------------------------|--------------------------------------------------------------|--------------------------------------------------|----------------------------------------------------------|
| Flag | Usage | Can serve blobs? | Usage | Can serve blobs? |
| --prune-blobs false | Does not prune blobs since using the flag | Yes, for blobs since using the flag and for the past 18 days | Does not prune data columns since using the flag | No |
| --semi-supernode | - | - | Store half data columns | Yes, for blobs since using the flag for a max of 18 days |
| --supernode | - | - | Store all data columns | Yes, for blobs since using the flag for a max of 18 days |
While both `--supernode` and `--semi-supernode` can serve blobs, a supernode will be faster to respond to blobs queries as it skips the blob reconstruction step. Running a supernode also helps the network by serving the data columns to its peers.