Add Fusaka FAQ#16413
Conversation
taxmeifyoucan
requested review from
corwintines,
minimalsm,
pettinarip and
wackerow
as code owners
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wackerow
left a comment
wackerow
left a comment
There was a problem hiding this comment.
🔥 Overall looks great @taxmeifyoucan! Thanks again for the continued content updates here... left a set of comments ranging from structural, grammatical and some clerical and style-guide related. Tried to leave as many code suggestions as possible to make patching easier but may have missed some.
|
|
||
| Alongside PeerDAS, [a small change](https://eips.ethereum.org/EIPS/eip-7918) that improves the blob fee market is being introduced. It ensures that the blob fee market reacts efficiently to congestion and doesn't spiral down to 1 wei, guaranteeing L2s pay a meaningful fee for the compute and space that blobs impose on nodes. | ||
|
|
||
| ### What are Blob Parameter Only forks? {#what-are-blob-parameter-only-forks} |
There was a problem hiding this comment.
Similar here... is this a "frequently asked question" that isn't already specifically discussed in the dedicated BPO section above?
There was a problem hiding this comment.
The reason for many of these duplicates is that I originally intended this as a standalone FAQ page. But as we started FAQ section in here, I just added all in one page but let me know if you think it would make sense having separate. Otherwise happy to trim down the content, sorry about the redundancy
There was a problem hiding this comment.
Okay yeah, makes sense ❤️
I guess my general take on "FAQs" is we should first attempt to provide quality thought-out content to users that would cover as much as possible (which I think we've done a good job of through the rest of this page so far). Then, if there are particularly common questions that people ask where a concise answer could be provided, an FAQ can be handy to fill in those gaps, or concisely and more directly answer this frequent questions. I'd be cautious though of effectively using the FAQ approach for larger amounts of content.
Curious your take on these thoughts
There was a problem hiding this comment.
Thanks a lot for the input again! I removed some duplicate content and added missing piece on hardware. Feel free to edit it further down
Co-authored-by: wackerow <54227730+wackerow@users.noreply.github.com>
wackerow
left a comment
wackerow
left a comment
There was a problem hiding this comment.
Lgtm! Approving—will wait a bit before merging @nixorokish if you have any other input you'd like to add before pulling this in
|
sorry for the delay and thanks very much for all the review @wackerow - it lgtm! great job @taxmeifyoucan |
3 participants
Extends the FAQ section for Fusaka upgrade.
Couple things are missing, validator and supernode bandwidth requirements which are super clear at the moment. Will be added later
Cc @nixorokish
Preview link
https://deploy-preview-16413--ethereumorg.netlify.app/roadmap/fusaka