Add ERC: Parameterized Storage Keys#1455
Merged
eip-review-bot merged 10 commits intoethereum:masterfrom Jan 27, 2026
Merged
Conversation
Define a standard format for parameterized string keys used in EVM key-value storage. Keys with parameters use a colon and space separator (: ). This format was inspired by TOON format, and we acknowledge this preceding work.
Fix created date format and add internal links to ERC-8048/8049.
Collaborator
|
✅ All reviewers have approved. |
abcoathup
reviewed
Jan 7, 2026
abcoathup
reviewed
Jan 7, 2026
ERCS/erc-8119.md
Outdated
| title: Key Parameters | ||
| description: A standard format for parameterized string keys used in EVM key-value storage. | ||
| author: Prem Makeig (@nxt3d) | ||
| discussions-to: |
Contributor
There was a problem hiding this comment.
Please create a discussions topic in Eth Magicians with a link to this PR
https://ethereum-magicians.org/c/ercs/57
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
File renamed from erc-key-parameters.md to erc-8119.md to reflect assigned ERC number.
Update discussions-to field with forum post URL and add forum post draft.
3 tasks
xinbenlv
reviewed
Jan 13, 2026
xinbenlv
reviewed
Jan 13, 2026
xinbenlv
reviewed
Jan 13, 2026
ERCS/erc-8119.md
Outdated
| For string keys used in EVM key-value storage (e.g., `mapping(string => bytes)` in Solidity, hash maps in Vyper, or equivalent structures in other EVM-compatible languages): | ||
|
|
||
| 1. The base key name and parameter MUST be separated by a colon (`:`) followed by a single space (` `). | ||
| 2. The parameter value MAY be any string that does not contain `: ` (colon followed by space). Colons without a following space are allowed in the parameter value. |
Collaborator
There was a problem hiding this comment.
How to escape if value needs to contain :?
Define <key-label>: <key-parameter>, restrict key-label to ASCII without spaces, and add UTF-8 parameter examples.
eip-review-bot
changed the title
- Restrict key-labels to printable ASCII (0x21-0x7E), excluding control characters, space, and DEL - Allow key-parameters to contain any UTF-8 string including `: ` - Clarify that parsing uses the first `: ` as separator - Add examples with URLs and special characters (%gain, $price, #tag) - Update test cases to reflect new rules
nxt3d
changed the title
|
The commit c8af122 (as a parent of c0feb92) contains errors. |
3 tasks
|
|
||
| ## Specification | ||
|
|
||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. |
Member
There was a problem hiding this comment.
Could you link the RFCs as seen here? https://eips.ethereum.org/EIPS/eip-1#rfc-2119-and-rfc-8174
eip-review-bot
changed the title
eip-review-bot
approved these changes
Jan 27, 2026
Collaborator
eip-review-bot
left a comment
eip-review-bot
left a comment
There was a problem hiding this comment.
All Reviewers Have Approved; Performing Automatic Merge...
nivekpraht
approved these changes
Feb 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds ERC-8119: Parameterized Storage Keys, a standard format for parameterized string keys used in EVM key-value storage.
Description
This ERC defines a standard format for parameterized string keys where keys with parameters use a colon and space separator (
:). This provides a uniform, readable, and parseable format for keys that need to represent multiple instances or variations of the same metadata type.Key Features
:) for parameterized keysRelated Standards
This ERC can be used by standards such as:
Inspiration
This format was inspired by TOON format (developed by Johann Schopplich), and we acknowledge this preceding work.