search

hashgraph / hedera-mirror-node-explorer

Hedera Mirror Node Explorer for the Hedera Hashgraph DLT.
Apache License 2.0
14 stars 9 forks source link

Call trace entries contain the same parameters for each call #1117

Closed vea-vecturne closed 2 weeks ago

vea-vecturne commented 3 weeks ago

Description

We noticed something in the mirror node for a transaction that seems a bit off.

https://hashscan.io/mainnet/transaction/1718213391.883698003

For each call under call trace, the input parameters are the same. Its confusing because each call may take different parameters. The actions endpoint seems to return different input data for each call:

https://mainnet-public.mirrornode.hedera.com/api/v1/contracts/results/0x8a89ee664b973de1f3225b8c2118d883a4f64219c202af0a4604629ff2441ddb/actions?limit=100

Each input is a tuple parameter, but only the initial call takes the tuple parameter, not the subsequent calls.

image

Steps to reproduce

Observe the mirror node call trace for the link above and the actions endpoint to see the difference

Additional context

No response

Hedera network

mainnet

Version

whatever version is live

Operating system

None

ericleponner commented 3 weeks ago

@vea-vecturne Thanks for reporting.