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

Flag EVM precompile contracts correctly #1567

Open
Neurone opened this issue Dec 16, 2024 · 0 comments
Open

Flag EVM precompile contracts correctly #1567

Neurone opened this issue Dec 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Neurone
Copy link
Contributor

Neurone commented Dec 16, 2024

Problem

When exploring the call trace of an Ethereum transaction (i.e., https://hashscan.io/mainnet/transaction/1734374863.173640000), the EVM precompiled contracts are not properly marked, and they seem to be normal contracts that I can click and explore.

Additionally, even recognized precompiled smart contracts (i.e., Hedera Token Service System Contract) are linkable, leading users to misleading 404 pages (not found contracts, or not found tokens in the case of unrecognized system contracts).

Immagine 2024-12-16 234429 Immagine 2024-12-16 234618 Immagine 2024-12-16 234637

Solution

  • Name the EVM precompile contracts according to the common names (i.e. 0x2 = ecRecover, 0x3 SHA2-256, etc., see: https://www.evm.codes/precompiled)
  • Link the precompiled contracts to documentation pages (Hedera Doc for Hedera-specific contracts, evm.codes for EVM system contracts).

Alternatives

No response

@Neurone Neurone added the enhancement New feature or request label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant