Skip to content

Commit

Permalink
Update EIP-7723: Escape Latex
Browse files Browse the repository at this point in the history
Merged by EIP-Bot.
  • Loading branch information
timbeiko authored Dec 27, 2024
1 parent 66f6e9b commit 7536f3a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion EIPS/eip-7723.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Before the Upgrade Meta EIP is moved to `Final`, the `Scheduled for Inclusion` s

### Upgrade Devnets

When preparing a network upgrade, client developers typically implement EIPs first on an ephemeral test network (upgrade devnet) to verify client interoperability, before deploying to long-lived test networks. These upgrade devnets follow a naming convention of $upgradeName-devnet-$version (e.g. pectra-devnet-0 for the first upgrade devnet of the Pectra network upgrade, dencun-devnet-1 for the second upgrade devnet of the Dencun update, etc).
When preparing a network upgrade, client developers typically implement EIPs first on an ephemeral test network (upgrade devnet) to verify client interoperability, before deploying to long-lived test networks. These upgrade devnets follow a naming convention of \$upgradeName-devnet-\$version (e.g. pectra-devnet-0 for the first upgrade devnet of the Pectra network upgrade, dencun-devnet-1 for the second upgrade devnet of the Dencun update, etc).

Since client developers' ability to include EIPs in a network upgrade is constrained by what can be implemented and tested in these upgrade devnets, the [Considered for Inclusion](#considered-for-inclusion) and [Scheduled for Inclusion](#scheduled-for-inclusion) sections below propose aligning these statuses with EIPs' implementation status in upgrade devnets.

Expand Down

0 comments on commit 7536f3a

Please sign in to comment.