Skip to content

Add BPO Folder#1894

Open
poojaranjan wants to merge 4 commits into
ethereum:masterfrom
poojaranjan:P-bpo
Open

Add BPO Folder#1894
poojaranjan wants to merge 4 commits into
ethereum:masterfrom
poojaranjan:P-bpo

Conversation

@poojaranjan
Copy link
Copy Markdown
Contributor

Add blob schedule and BPO upgrade parameter documentation to increase visibility into BPO progress, similar to how other Ethereum network upgrades are tracked.

This document provides a reference for Ethereum mainnet blob parameter schedules and BPO upgrades, including activation times and blob schedule parameters.
Added reference documents for blob scaling and BPO timelines.
Added guidelines for BPO upgrade documentation.
@taxmeifyoucan
Copy link
Copy Markdown
Member

I see this have been open for a while, I guess there are not many strong feelings for or against.

I am wondering, are there going to be many fork independent BPOs that would warrant this?

It feels like a bit too much overhead because I don't expect blobs widely changing all the time. For example if there were only BPOs after and maybe one fork in the future, not necessary to have a dedicated folder and it could live in more simple format under the fork. Just trying to keep the repo as lean as we can

@poojaranjan
Copy link
Copy Markdown
Contributor Author

Thanks for reviewing. Totally agree on keeping the repo lean.

That said, this PR is primarily informational and aimed at improving public information. Similar to other upgrade folders, it provides a clear entry point with pointers to relevant specs and discussions, rather than adding ongoing overhead.

Even if we don’t expect many independent BPO forks, having a dedicated place helps with discoverability and serves as a useful historical reference for how Blob Parameter Only changes were coordinated.

Given this, I’d suggest merging the PR for its value as a public-facing reference. We can always revisit and simplify if the structure proves unnecessary over time.

Updated the documentation to include references to Meta EIPs for BPO upgrades.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants