Skip to content

added the Verge, the Purge and the Splurge #432

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ojuschugh1
Copy link

@ojuschugh1 ojuschugh1 commented Apr 28, 2025

Description

This pull request adds the missing URGES sections—The Purge and The Splurge—to the Ethereum Protocol Roadmap wiki page, completing the previously half-populated table with detailed upgrade entries and references to Vitalik Buterin’s “Possible Futures” series and relevant EIPs. It also populates the Staking Economics track under The Scourge, fills out The Verge section with Data Availability Sampling and Verkle Tree Commitments, and updates the Resources section to include Domothy’s Week 5 presentation.

Closes Issue #294.


PR Checklist

  • I have read the Contributor Guidelines and understand the PR requirements.
  • I describe my changes clearly in this PR description.
  • I have asked the original content authors for review (where applicable).
  • I will share this PR in the EPF Discord for broader feedback.
  • [] I have reviewed my changes and there are no typos.

the Purge

the Splurge
Copy link

Hi @ojuschugh1,

⚠️ Potential typos found in your pull request:

  • 📄 ./docs/wiki/research/roadmap.md (line(s) 112):
    1. ❌ bundlers
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 113):
    1. ❌ PQS
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ toolchain
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ HOL
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ benchmarking

ℹ️ How to fix this error:

  1. If these are actual typos:

    • Open the files at the specified line numbers and fix them
  2. If these are names or one-off nouns:

    • Wrap them in <name> tags
    • Example: <name>Alex Pereira</name>
    • Use this for people's names or unique terms that appear rarely
  3. If these are valid terms:

    • Add them to wordlist.txt (one word per line)
    • Terms must be plain text without spaces/special chars
    • The list is case-insensitive
  4. If these are code terms:

    • Wrap them in backticks (`) in your markdown

ℹ️ Checking for typos locally

  1. Install aspell for your platform
  2. Navigate to project root and run:
for f in **/*.md ; do echo $f ; aspell --lang=en_US --mode=markdown --home-dir=. --personal=wordlist.txt --ignore-case=true --camel-case --add-sgml-skip nospellcheck list < $f | sort | uniq -c ; done

Learn more about wordlist format

@ojuschugh1 ojuschugh1 changed the title added the Verge added the Verge, the Purge and the Splurge Apr 28, 2025
Copy link
Contributor

@taxmeifyoucan taxmeifyoucan left a comment

Choose a reason for hiding this comment

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

This is great, thanks for finishing the roadmap!

Copy link

github-actions bot commented May 7, 2025

Hi @ojuschugh1,

⚠️ Potential typos found in your pull request:

  • 📄 ./docs/wiki/research/roadmap.md (line(s) 112):
    1. ❌ bundlers
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 113):
    1. ❌ PQS
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ toolchain
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ HOL
  • 📄 ./docs/wiki/research/roadmap.md (line(s) 114):
    1. ❌ benchmarking

ℹ️ How to fix this error:

  1. If these are actual typos:

    • Open the files at the specified line numbers and fix them
  2. If these are names or one-off nouns:

    • Wrap them in <name> tags
    • Example: <name>Alex Pereira</name>
    • Use this for people's names or unique terms that appear rarely
  3. If these are valid terms:

    • Add them to wordlist.txt (one word per line)
    • Terms must be plain text without spaces/special chars
    • The list is case-insensitive
  4. If these are code terms:

    • Wrap them in backticks (`) in your markdown

ℹ️ Checking for typos locally

  1. Install aspell for your platform
  2. Navigate to project root and run:
for f in **/*.md ; do echo $f ; aspell --lang=en_US --mode=markdown --home-dir=. --personal=wordlist.txt --ignore-case=true --camel-case --add-sgml-skip nospellcheck list < $f | sort | uniq -c ; done

Learn more about wordlist format

@ojuschugh1
Copy link
Author

ojuschugh1 commented May 7, 2025

Hi @taxmeifyoucan ,
Thanks for the review and your kind words—they really boost my morale! I’ll fix the typo as soon as possible; I’ve been busy exploring project proposal ideas for EPF Cohort 6, just trying them and getting my hands dirty in case I get selected. 🙂

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