This EIP extends ERC-1046-compatible token types (notably, ERC-20 and ERC-1155 by introducing a multiplier field to the metadata schema, altering how user-facing balances are displayed.
Many projects necessitate the creation of various types of tokens, both fungible and non-fungible. While certain standards are ideal for this purpose, they lack support for fractional tokens. Additionally, some tokens may require built-in inflation or deflation mechanisms, or may wish to allow transfers in unconventional increments, such as 0.5.
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.
The MultiplierMetadata interface MUST be implemented in the resolved ERC-1046 tokenURI of tokens that use a multiplier:
Token contracts MUST NOT have a method named decimals if a multiplier is used.
Employing strings for numerical representation offers enhanced precision when needed. The use of a multiplier instead of decimals facilitates increments other than powers of 10, and ensures seamless handling of inflation or deflation. Utilizing ERC-1046 promotes gas efficiency in the majority of cases.
This EIP is incompatible with any method named decimals in ERC-1046-compatible token standards or the ERC-1046 decimals field.
Improper handling of the multiplier field may lead to rounding errors, potentially exploitable by malicious actors. Contracts MUST process multipliers accurately to avoid such issues. The multiplier MUST be positive (‘0’ is not positive) to avert display issues. Particularly large or small multipliers MAY pose display challenges, yet wallets SHOULD endeavor to display the full number without causing UI/UX or additional security issues.
Copyright and related rights waived via CC0.