From 4a1ce4f1e45946b8b7639105788445df0efda7bf Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Fri, 19 Jul 2024 16:03:17 +0200 Subject: [PATCH 1/4] add postel's law SHOULD to the eip-55 paragraph per implementer feedback --- eip155/caip10.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/eip155/caip10.md b/eip155/caip10.md index 476dcaae..6369f821 100644 --- a/eip155/caip10.md +++ b/eip155/caip10.md @@ -32,11 +32,11 @@ Note that a given address cannot be assumed to work on all current and future ne ## Syntax -Ethereum addresses were, historically, case-insensitive and normalized to use -all-lowercase letters (`abcdef`) like most hexadecimal numeric types. With the -ratification of [EIP-55][], however, a particular normalization of lowercase- and -uppercase- `abcdefABCDEF` characters was invented as an efficient form of -checksum. See [EIP-55][] for specification. +Ethereum addresses were, historically, case-insensitive and normalized to use all-lowercase letters (`abcdef`) like most hexadecimal numeric types. +With the ratification of [EIP-55][], however, a particular normalization of lowercase- and uppercase- `abcdefABCDEF` characters was invented as an efficient form of checksum. +Most implementations will still accept lowercase addresses but produce only checksum-case addresses, as many transaction-builders will validate not just against a regular expression but also against an EIP-55 checksum. +Anywhere ["Postel's Law"][postel] can apply, implementers SHOULD produce checksum-case secure addresses (whether in CAIP-10 or native format), and SHOULD accept both checksum case and legacy lowercase addresses, except where the security concerns of the particular usecase outweigh interoperability. +See [EIP-55][] for specification. The chain ID will be used to represent blockchain except special case of 0 as chainID to represent EOA. @@ -104,7 +104,7 @@ As the Ethereum namespace evolved, user-agents that connect to dapps through an [EIP-55]: https://eips.ethereum.org/EIPS/eip-55 [ERC-20]: https://eips.ethereum.org/EIPS/eip-20 [ERC-721]: https://eips.ethereum.org/EIPS/eip-721 - +[postel]: https://www.rfc-editor.org/rfc/rfc760#section-3.2 ## Rights From 102b4d34cb3d80e7d1f4fb6e3c57b71abfe8af46 Mon Sep 17 00:00:00 2001 From: Bumblefudge Date: Thu, 15 Aug 2024 17:49:33 +0200 Subject: [PATCH 2/4] Update eip155/caip10.md --- eip155/caip10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/eip155/caip10.md b/eip155/caip10.md index 6369f821..5f3e1090 100644 --- a/eip155/caip10.md +++ b/eip155/caip10.md @@ -33,7 +33,7 @@ Note that a given address cannot be assumed to work on all current and future ne ## Syntax Ethereum addresses were, historically, case-insensitive and normalized to use all-lowercase letters (`abcdef`) like most hexadecimal numeric types. -With the ratification of [EIP-55][], however, a particular normalization of lowercase- and uppercase- `abcdefABCDEF` characters was invented as an efficient form of checksum. +With the ratification of [ERC-55][], however, a particular normalization of lowercase- and uppercase- `abcdefABCDEF` characters was invented as an efficient form of checksum. Most implementations will still accept lowercase addresses but produce only checksum-case addresses, as many transaction-builders will validate not just against a regular expression but also against an EIP-55 checksum. Anywhere ["Postel's Law"][postel] can apply, implementers SHOULD produce checksum-case secure addresses (whether in CAIP-10 or native format), and SHOULD accept both checksum case and legacy lowercase addresses, except where the security concerns of the particular usecase outweigh interoperability. See [EIP-55][] for specification. From fb922c634207f70e49bb32dfdfc930599baa2081 Mon Sep 17 00:00:00 2001 From: Bumblefudge Date: Thu, 15 Aug 2024 17:49:56 +0200 Subject: [PATCH 3/4] Update eip155/caip10.md --- eip155/caip10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/eip155/caip10.md b/eip155/caip10.md index 5f3e1090..afa272dc 100644 --- a/eip155/caip10.md +++ b/eip155/caip10.md @@ -101,7 +101,7 @@ As the Ethereum namespace evolved, user-agents that connect to dapps through an [ERC-4361]: https://eips.ethereum.org/EIPS/eip-4361 [EIP-1193]: https://eips.ethereum.org/EIPS/eip-1193 [EIP-155]: https://eips.ethereum.org/EIPS/eip-155 -[EIP-55]: https://eips.ethereum.org/EIPS/eip-55 +[ERC-55]: https://eips.ethereum.org/EIPS/eip-55 [ERC-20]: https://eips.ethereum.org/EIPS/eip-20 [ERC-721]: https://eips.ethereum.org/EIPS/eip-721 [postel]: https://www.rfc-editor.org/rfc/rfc760#section-3.2 From 100b965a5345130b3e53ec15d5442d0b867fb325 Mon Sep 17 00:00:00 2001 From: bumblefudge Date: Thu, 12 Sep 2024 17:23:37 +0200 Subject: [PATCH 4/4] eip/erc 155 fix --- eip155/caip10.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/eip155/caip10.md b/eip155/caip10.md index afa272dc..6369f821 100644 --- a/eip155/caip10.md +++ b/eip155/caip10.md @@ -33,7 +33,7 @@ Note that a given address cannot be assumed to work on all current and future ne ## Syntax Ethereum addresses were, historically, case-insensitive and normalized to use all-lowercase letters (`abcdef`) like most hexadecimal numeric types. -With the ratification of [ERC-55][], however, a particular normalization of lowercase- and uppercase- `abcdefABCDEF` characters was invented as an efficient form of checksum. +With the ratification of [EIP-55][], however, a particular normalization of lowercase- and uppercase- `abcdefABCDEF` characters was invented as an efficient form of checksum. Most implementations will still accept lowercase addresses but produce only checksum-case addresses, as many transaction-builders will validate not just against a regular expression but also against an EIP-55 checksum. Anywhere ["Postel's Law"][postel] can apply, implementers SHOULD produce checksum-case secure addresses (whether in CAIP-10 or native format), and SHOULD accept both checksum case and legacy lowercase addresses, except where the security concerns of the particular usecase outweigh interoperability. See [EIP-55][] for specification. @@ -101,7 +101,7 @@ As the Ethereum namespace evolved, user-agents that connect to dapps through an [ERC-4361]: https://eips.ethereum.org/EIPS/eip-4361 [EIP-1193]: https://eips.ethereum.org/EIPS/eip-1193 [EIP-155]: https://eips.ethereum.org/EIPS/eip-155 -[ERC-55]: https://eips.ethereum.org/EIPS/eip-55 +[EIP-55]: https://eips.ethereum.org/EIPS/eip-55 [ERC-20]: https://eips.ethereum.org/EIPS/eip-20 [ERC-721]: https://eips.ethereum.org/EIPS/eip-721 [postel]: https://www.rfc-editor.org/rfc/rfc760#section-3.2