You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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
The text was updated successfully, but these errors were encountered:
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).
Solution
Alternatives
No response
The text was updated successfully, but these errors were encountered: