Skip to content
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.

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

Transaction with CONTRACT_NEGATIVE_VALUE prevents entire block from being retrieved #3367

Closed
ted-yeh-vc opened this issue Jan 9, 2025 · 1 comment · Fixed by #3387 or #3435
Closed
Assignees
Labels
bug Something isn't working
Milestone

Comments

@ted-yeh-vc
Copy link
Contributor

Description

It seems like eth_getBlockByNumber fails because one of the transactions in the block was a CONTRACT_NEGATIVE_VALUE failure. The expectation is for the block to be successfully returned.

Steps to reproduce

  1. call eth_getBlockByNumber on block 73298898
  2. see "Error invoking RPC: Invalid value - cannot pass negative number" response

The problematic transaction is here

Additional context

No response

Hedera network

mainnet

Version

v0.61.0

Operating system

Linux

@ted-yeh-vc ted-yeh-vc added the bug Something isn't working label Jan 9, 2025
@Nana-EC Nana-EC moved this from Backlog to Sprint Backlog in Smart Contract Sprint Board Jan 9, 2025
@ted-yeh-vc
Copy link
Contributor Author

Similarly, calling eth_getTransactionByHash on the problematic transaction produces a Unknown error invoking RPC response, but the logs also say "Error invoking RPC: Invalid value - cannot pass negative number".

payload:

{
    "jsonrpc": "2.0",
    "method": "eth_getTransactionByHash",
    "params": [
			"0xe9abca1749b140dcacadb4f490c74c75ae607cd4ac2249bf018702e5ab6432e2"
		],
    "id": "73"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment