Add EIP: Opcodes Per Second

[MASDXI]

Opcodes Per Second is an additional factor for assessing EVM implementation performance.

[eth-bot]

File EIPS/eip-7852.md

Requires 1 more reviewers from @g11tech, @lightclient, @SamWilsn, @xinbenlv

[github-actions]

The commit 134c07d (as a parent of 0a62a5a) contains errors.
Please inspect the Run Summary for details.

[abcoathup]

Suggested change

	eip: XXXX
	eip: 7852

Assigning next sequential EIP/ERC/RIP number.
Numbers are assigned by editors & associates.

Please also update the filename.

[abcoathup]

Suggested change

	discussions-to: https://ethereum-magicians.org/t/eip-xxxx-opps-opcode-per-second/22179
	discussions-to: https://ethereum-magicians.org/t/eip-7852-opps-opcode-per-second/22179

Updated Eth Magicians with assigned EIP number.

For the discussions post you don't need to copy/paste your EIP text.
Please use the below template:

Discussion topic for EIP-XXXX

Update Log

This section should list significant updates to the EIP as the specification evolves. The first entry should be the PR to create the EIP. The recommended format for log entries is:

• yyyy-mm-dd: Single sentence description, commit link to commit

For example, using EIP-1:

• 2024-06-05: Enable external links to Chain Agnostic Improvement Proposals (CAIPs), commit 32dc740.
  ...

Fill in the log for the EIP's initial draft below:

• yyyy-mm-dd: initial draft

External Reviews

This section should list notable reviews the EIP has received from the Ethereum community. These can include specific comments on this forum, timestamped audio/video exchanges, formal audits, or other external resources. This section should be the go-to for readers to understand the community's current assessment of the EIP. Aim for neutrality, quality & thoroughness over "cherry-picking" the most favorable reviews.

The recommended format for entries is:

• yyyy-mm-dd: Single sentence description, link to review

For example, using EIP-1559, one entry could be:

• 2020-12-01: "An Economic Analysis of EIP-1559", by Tim Roughgarden, full report

None as of yyyy-mm-dd.

Outstanding Issues

This section should highlight outstanding issues about the EIP, and, if possible, link to forums where these are being addressed. This section should allow readers to quickly understand what the most important TODOs for the EIP are, and how to best contribute. Once issues are resolved, they should be checked off with a note giving context on the resolution.

The recommended format for new entries is:

• yyyy-mm-dd: Issue description, link to issue

Once issues are addressed, these becomes:

• yyyy-mm-dd: Issue description, link to issue
  • yyyy-mm-dd: Resolution description, link to resolution

For example, using EIP-3675, one entry could be:

• 2021-07-08: Repurpose the DIFFICULTY opcode, tracking issue
  • 2021-10-30: Introduce EIP-4399, EIP PR

If there are any known outstanding issues currently, fill them out now.

None as of yyyy-mm-dd.