Updating EL specs to include EIP-7702 type 4 transaction

[ParthRathix0]

Wiki PR Checklist

Thank you for contributing to the Protocol Wiki! Before you open a PR, make sure to read information for contributors and take a look at following checklist:

• Describe your changes, substitute this text with the information
• If you are touching an existing piece of content, ask the original creator for review
• If you need feedback for your content from wider community, share the PR in our Discord
• Review changes to ensure there are no typos, see instructions bellow

Solves #438

Summary of Changes (EIP-7702 Integration)

Where	What	Why
### Effective Gas Price & Priority Fee	Added \lor 4 to the conditions in the effectiveGasPrice and priorityFee equations.	Type 4 transactions utilize the standard EIP-1559 fee pricing model.
### Max Gas Fee	Added \lor 4 to the Type 2 condition in the maxGasFee equation.	Type 4 transactions calculate their maximum gas fee identically to Type 2.
### Transaction Intrinsic Validity	Added \lor 4 to the max fee bounds check and the definition of variable $m$.	Ensures Type 4 transactions undergo the required EIP-1559 validity validations.
#### Substate initialization	Appended \lor 4 to the transaction type condition block for access lists.	Type 4 transactions support and process access lists just like Types 1, 2, and 3.
## Gas Accounting Examples	Appended new sub-section: "Example 3: Set EOA Code Transaction".	Provides a practical breakdown of Type 4 parameters (authorizationList) and gas overhead.

[github-actions]

Hi @ParthRathix0,

⚠️ Potential typos found in your pull request:

• 📄 ./docs/readme.md (line(s) 7,23):
  1. ❌ annualy
• 📄 ./docs/readme.md (line(s) 7,23):
  1. ❌ annualy
• 📄 ./docs/wiki/EL/el-specs.md (line(s) 1093):
  1. ❌ Finalisation
• 📄 ./docs/wiki/EL/el-data-structures-summary.md (line(s) 8,21):
  1. ❌ prev

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

[github-actions]

Hi @ParthRathix0,

⚠️ Potential typos found in your pull request:

• 📄 ./docs/readme.md (line(s) 23):
  1. ❌ annualy
• 📄 ./docs/wiki/EL/el-specs.md (line(s) 1093):
  1. ❌ Finalisation
• 📄 ./docs/wiki/EL/el-data-structures-summary.md (line(s) 8,21):
  1. ❌ prev

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

[github-actions]

Hi @ParthRathix0,

⚠️ Potential typos found in your pull request:

• 📄 ./docs/readme.md (line(s) 23):
  1. ❌ annualy
• 📄 ./docs/wiki/EL/el-data-structures-summary.md (line(s) 8,21):
  1. ❌ prev

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