From 47e30db9f3d9c446552c3bb1d80ce1b3648d25d7 Mon Sep 17 00:00:00 2001 From: Nick Johnson Date: Mon, 20 Nov 2017 13:06:48 +0000 Subject: [PATCH] Update eip-draft-returndata.md --- EIPS/eip-draft-returndata.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/EIPS/eip-draft-returndata.md b/EIPS/eip-draft-returndata.md index 6473da85..09afc15e 100644 --- a/EIPS/eip-draft-returndata.md +++ b/EIPS/eip-draft-returndata.md @@ -1,11 +1,11 @@ ## Preamble - EIP: - Title: Embedding transaction return data in receipts + EIP: 658 + Title: Embedding transaction status code in receipts Author: Nick Johnson Type: Standard Track Category Core - Status: Draft + Status: Final Created: 2017-06-30 Requires: 140 Replaces: 98 @@ -22,7 +22,7 @@ Full nodes can provide RPCs to get a transaction return status and value by repl Instead, we propose to replace the intermediate state root, already obsoleted by EIP98, with the return status (1 for success, 0 for failure). This both allows callers to determine success status, and remedies the previous omission of return data from the receipt. ## Specification -For blocks where block.number >= METROPOLIS_FORK_BLKNUM, the intermediate state root is replaced by a status code, 0 indicating failure (due to any operation that can cause the transaction or top-level call to revert) and 1 indicating success. +For blocks where block.number >= BYZANTIUM_FORK_BLKNUM, the intermediate state root is replaced by a status code, 0 indicating failure (due to any operation that can cause the transaction or top-level call to revert) and 1 indicating success. ## Rationale This constitutes a minimal possible change that permits fetching the success/failure state of transactions, preserving existing capabilities with minimum disruption or additional work for Metropolis.