Skip to content

Commit

Permalink
Update ERC-7528: ERC 7528 Clarifications
Browse files Browse the repository at this point in the history
Merged by EIP-Bot.
  • Loading branch information
Joeysantoro authored Dec 13, 2023
1 parent 8358b94 commit 1967eb3
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions ERCS/erc-7528.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@ status: Review
type: Standards Track
category: ERC
created: 2023-10-03
requires: 20, 4626
requires: 20, 155, 4626
---

## Abstract

The following standard proposes a convention for using the address `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` in all contexts where an address is used to represent ETH in the same capacity as an [ERC-20](./eip-20.md) token. This would apply to both events where an address field would denote ETH or an [ERC-20](./eip-20.md) token, as well as discriminators such as the `asset` field of an [ERC-4626](./eip-4626.md) vault.
The following standard proposes a convention for using the address `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` in all contexts where an address is used to represent ETH in the same capacity as an [ERC-20](./eip-20.md) token. This would apply to both events where an address field would denote ETH or an [ERC-20](./eip-20.md) token, as well as discriminators such as the `asset` field of an [ERC-4626](./eip-4626.md) vault.

This standard generalizes to other EVM chains where the native asset is not ETH.

Expand All @@ -27,15 +27,17 @@ In addition, protocols might create separate events for handling ETH native case

One intended use case for the standard is [ERC-4626](./eip-4626.md) compliant LSTs which use ETH as the `asset`. This extends the benefits and tooling of [ERC-4626](./eip-4626.md) to LSTs and integrating protocols.

This standard allows protocols and off-chain data infrastructure to coordinate around a shared understanding that any time `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` is used as an address in an [ERC-20](./eip-20.md) context, it means ETH.
This standard allows protocols and off-chain data infrastructure to coordinate around a shared understanding that any time `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` is used as an address in an [ERC-20](./eip-20.md) context, it means ETH.

## Specification

This standard applies for all components of smart contract systems in which an address is used to identify an [ERC-20](./eip-20.md) token, and where native ETH is used in certain instances in place of an [ERC-20](./eip-20.md) token. The usage of the term Token below means ETH or an [ERC-20](./eip-20.md) in this context.

Any fields or events where an [ERC-20](./eip-20.md) address is used, yet the underlying Token is ETH, the address field MUST return `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE`
Any fields or events where an [ERC-20](./eip-20.md) address is used, yet the underlying Token is ETH, the address field MUST return `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee`

Any fields or events where the Token is a non-enshrined wrapped ERC-20 version of ETH (i.e WETH9) MUST use that Token's address and MUST NOT use `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE`.
Any fields or events where the Token is a non-enshrined wrapped ERC-20 version of ETH (i.e WETH9) MUST use that Token's address and MUST NOT use `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee`.

Where appropriate, the address should be checksummed. E.g. the [EIP-155](./eip-155.md) checksum is `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE`.

## Rationale

Expand All @@ -45,7 +47,7 @@ Many existing implementations of the same use case as this standard use addresse

Ultimately, all of these addresses collide with potential precompile addresses and are less distinctive as identifiers for ETH.

`0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE` has the most current usage, is distinctive, and would not collide with any precompiles. These benefits outweigh the potential gas benefits of other alternatives.
`0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` has the most current usage, is distinctive, and would not collide with any precompiles. These benefits outweigh the potential gas benefits of other alternatives.

## Backwards Compatibility

Expand Down

0 comments on commit 1967eb3

Please sign in to comment.