Skip to content

Flag EVM precompile contracts correctly #1567

@Neurone

Description

@Neurone

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

Metadata

Metadata

Assignees

Labels

P1An issue impacting production environments or impacting multiple releases or multiple individualsenhancementNew feature or requestreleasedsmart contractsFeatures that involve smart contracts

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions