Skip to content

Conversation

@ParthSinghPS
Copy link
Contributor

Summary

Adds a concise explanation for the I_blobVersionedHashes execution
environment parameter.

Motivation

The parameter previously lacked a clear description, making it unclear
what data is exposed to the EVM for blob-carrying transactions.

Changes

  • Documented I_blobVersionedHashes as the ordered list of versioned hashes
    of blobs attached to the current transaction

Spec reference

EIP-4844 (Proto-Danksharding)

@github-actions
Copy link

Hi @ParthSinghPS,

⚠️ Potential typos found in your pull request:

  • 📄 ./docs/eps/week1.md (line(s) 134):
    1. ❌ resleased
  • 📄 ./docs/eps/schedule.md (line(s) 35):
    1. ❌ Rakita
  • 📄 ./docs/wiki/testing/consensus-spec-tests.md (line(s) 15):
    1. ❌ symlinks
  • 📄 ./docs/wiki/testing/consensus-spec-tests.md (line(s) 23):
    1. ❌ incorect
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 3,5,6,9,15,17,19,29,57,83,99,110,186):
    1. ❌ ectra
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 59,63,65,121,150,152,186,197,199):
    1. ❌ sys
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 152,199):
    1. ❌ asm
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 51,114,140,152,199,237,241):
    1. ❌ eas
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 59,63,65,121,150,152,186,197,199):
    1. ❌ sys
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 152,199):
    1. ❌ asm
  • 📄 ./docs/wiki/pectra-faq.md (line(s) 51,114,140,152,199,237,241):
    1. ❌ eas
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 13):
    1. ❌ orginally
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 29):
    1. ❌ multiaddress
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 31):
    1. ❌ Multiaddress
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 31):
    1. ❌ Multiaddress
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 66):
    1. ❌ negociation
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 75):
    1. ❌ Multiaddrs
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 80):
    1. ❌ proactivily
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 56,82,128,279):
    1. ❌ kad
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 91):
    1. ❌ multihashes
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 91,97,281):
    1. ❌ multihash
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 101):
    1. ❌ Multihash
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 107):
    1. ❌ multibase
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 109):
    1. ❌ establised
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 126):
    1. ❌ Multicast
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 128,131):
    1. ❌ multiaddrs
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 128,131):
    1. ❌ multiaddrs
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 149):
    1. ❌ mututal
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 159):
    1. ❌ rount
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 163):
    1. ❌ Gossibhub
  • 📄 ./docs/wiki/CL/cl-networking.md (line(s) 160,171):
    1. ❌ gossibsub

ℹ️ 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

@taxmeifyoucan
Copy link
Contributor

Thanks for adding the explanation, good catch! This PR is also pushing the commit with picture from #472 so it's blocked by that

@ParthSinghPS
Copy link
Contributor Author

Not a problem , I will close this one and open a new PR with only this as the change.

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