From 345d9eedd5b64d9e67d2bb99210dc05f4212b0f3 Mon Sep 17 00:00:00 2001 From: Nick Mudge Date: Sun, 19 Jul 2020 00:41:49 -0400 Subject: [PATCH] Update eip-1155 errata. (#2800) --- EIPS/eip-1155.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-1155.md b/EIPS/eip-1155.md index cde7d53e..e3f41131 100644 --- a/EIPS/eip-1155.md +++ b/EIPS/eip-1155.md @@ -592,7 +592,7 @@ The `name` function (for human-readable asset names, on-chain) was removed from ### Upgrades -The requirement to emit `TransferSingle` or `TransferBatch` on balance change implies that a valid implementation of ERC-1155 redeploying to a new contract address MUST emit events from the new contract address to replicate the deprecated contract final state. It is valid to only emit a minimal number of events to reflect only the final balance and omit all the transactions that led to that state. The event emit requirement is to ensure that the current state of the contract can always be traced only through events. To alleviate the need to emit events when changing contract address, consider using the proxy pattern, such as described in ERC-1538. This will also have the added benefit of providing a stable contract address for users. +The requirement to emit `TransferSingle` or `TransferBatch` on balance change implies that a valid implementation of ERC-1155 redeploying to a new contract address MUST emit events from the new contract address to replicate the deprecated contract final state. It is valid to only emit a minimal number of events to reflect only the final balance and omit all the transactions that led to that state. The event emit requirement is to ensure that the current state of the contract can always be traced only through events. To alleviate the need to emit events when changing contract address, consider using the proxy pattern, such as described in [EIP-2535](https://eips.ethereum.org/EIPS/eip-2535). This will also have the added benefit of providing a stable contract address for users. ### Design decision: Supporting non-batch