Skip to content

Add EIP: Emit log on revert #9390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Mar 25, 2025
+52 −0
Merged

Add EIP: Emit log on revert #9390

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
d509968
Add new EIP
shohamc1 Feb 20, 2025
aede0ec
Spelling and grammar
shohamc1 Feb 22, 2025
9576cf4
Update EIP
shohamc1 Feb 25, 2025
f011351
Expound rationale
shohamc1 Feb 25, 2025
c1e9035
Update and rename eip-xxxx.md to eip-7889.md
SamWilsn Feb 25, 2025
2293717
Update discussion link
shohamc1 Feb 26, 2025
40075ce
Add TODO tag
shohamc1 Mar 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions EIPS/eip-7889.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
eip: 7889
title: Emit log on revert
description: Top level reverts emit a log with revert message
author: Shoham Chakraborty (@shohamc1), Alex Forshtat (@forshtat)
discussions-to: https://ethereum-magicians.org/t/eip-7889-emit-log-on-revert/22918
status: Draft
type: Standards Track
category: Core
created: 2025-02-20
---

## Abstract

All calls to the REVERT opcode with non-zero size must emit a log with revert data, making it accessible via standard RPC without the need for tracing.

## Motivation

Revert messages are currently inaccessible to users as they are not available via standard RPC. Instead, users have to request a node to trace the transaction and check the stack and memory at the moment when the REVERT opcode was executed.

This introduces overhead for users and nodes - users must make an additional request to find out why their transaction failed, and the node has to replay the full transaction (which may be slow and computationally expensive) to get back a relatively small piece of data.

Currently it is up to smart wallet developers to emit logs before a revert, however this is not a standard feature and thus cannot be relied upon by tools such as client libraries and block explorers. Making this log part of the protocol allows these tools to rely on logs for revert reasons.

## Specification

### Parameters

<!-- TODO -->

Check warning on line 29 in EIPS/eip-7889.md

View workflow job for this annotation

GitHub Actions / EIP Walidator 

warning[markdown-html-comments]: HTML comments are only allowed while `status` is one of: `Draft`, `Withdrawn`
  --> EIPS/eip-7889.md
   |
29 | <!-- TODO -->
   |
   = help: see https://ethereum.github.io/eipw/markdown-html-comments/

* `REVERTTOPIC`: `TBD`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a html <-- TODO --> tag for bot to track addressing this for going beyond draft

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

40075ce

* `DATA_LIMIT`: `TBD`

### Functionality

Whenever `REVERT` is called with non-zero size, emit a log identical to a LOG1 with the topic `REVERTTOPIC`. The log data is the raw bytes of the revert message. The data is truncated to `DATA_LIMIT`.

## Rationale

This is the simplest possible implementation that allows revert messages to be accessible via RPC methods. It does not require any changes to client libraries, or other RPC consumers as it is backward compatible. It does not introduce new RPC methods or new opcodes.

## Backwards Compatibility

Reverted transactions may now contain up to one log.

## Security Considerations

Reverted transactions must cost at least intrinsic gas (21000 gas), which is much more expensive than the LOG1 opcode (750 gas). Hence, this EIP does not introduce any new avenues to inflate Ethereum storage requirements. However, it is expected to increase the average number of logs.

## Copyright

Copyright and related rights waived via [CC0](../LICENSE.md).