Skip to content

Second-class EVM chains - Internal transactions parsing #11429

@gomesalexandre

Description

@gomesalexandre

Overview

Follow-up of #11426 to use debug_traceTransaction JSON-RPC method(or any other method that makes this work e.g Tenderly) to achieve internal transactions parsing.

Confirmed Tenderly does have support for Monad, Plasma, but not HyperEVM, which may be a blocker if we decide to go with that (would have to make HyperEVM work another way)

References and additional details

N/A

Acceptance Criteria

  • Note: Confirmed Monad and Plasma have support for Txs debug, but not HyperEVM Confirm that we indeed need Tenderly, first of all. For all intents and purposes, free nodes for those newer chains are the official ones, and we may well be able to use [debug_traceTransaction](https://docs.metamask.io/services/reference/mantle/json-rpc-methods/debug/debug_tracetransaction) (assuming node has debug flags enabled, which is not usually the case for free ones, but given those are official ones, worth taking a look)
  • Tenderly (or any other strategy) is used for Tx parsing to support internal transactions
  • Internal transaction parsing is happy and we decode internal transfers properly, resulting in correct execution price (can test with e.g anything on relay to XPL)

Need By Date

No response

Screenshots/Mockups

No response

Estimated effort

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions