Shibuya Node does not function as an EVM Tracing Node.

[Satish-Masa]

Description
I am trying to operate as an EVM Tracing Node at Shibuya Node, but it is not working, probably due to Runtime.
The node itself is synchronized and functions are fine except for the EVM Tracing Node.
Can you please help me figure out what the cause is?

I created the following Dockerfile image to operate Shibuya Node as an EVM Tracing Node.

FROM ubuntu:20.04

ARG VERSION

ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get upgrade -y \
    && apt install -y adduser libfontconfig1 wget git curl build-essential protobuf-compiler make clang pkg-config libssl-dev

RUN  mkdir /var/lib/astar && mkdir /var/lib/astar/wasm \
    && wget https://github.com/AstarNetwork/Astar/releases/download/v5.3.0/shibuya-runtime-95-substitute-tracing.wasm \
    && cp shibuya-runtime-95-substitute-tracing.wasm /var/lib/astar/wasm

RUN curl https://sh.rustup.rs -sSf | sh -s -- -y --default-toolchain stable \
    && . "$HOME/.cargo/env" \
    && git clone --recurse-submodules https://github.com/AstarNetwork/Astar.git -b ${VERSION} \
    && cd Astar && cargo build --release --features evm-tracing \
    && cp ./target/release/astar-collator /usr/local/bin/

EXPOSE 30333 30334 9933 9944

CMD ["/usr/local/bin/astar-collator" "-d" "/data"]

If you start with the above image, it will start as shown below.

- args:
            - '--pruning'
            - archive
            - '--name'
            - my-astar
            - '--chain'
            - shibuya
            - '--execution'
            - wasm
            - '--base-path'
            - /data
            - '--rpc-cors=all'
            - '--rpc-external'
            - '--ws-external'
            - '--enable-evm-rpc'
            - '--ethapi=txpool,debug,trace'
            - '--wasm-runtime-overrides'
            - /var/lib/astar/wasm

2023-04-06 03:41:49 Astar Collator
2023-04-06 03:41:49 ✌️  version 5.3.0-afcc6d7c9ac
2023-04-06 03:41:49 ❤️  by Stake Technologies <[email protected]>, 2019-2023
2023-04-06 03:41:49 📋 Chain specification: Shibuya Testnet
2023-04-06 03:41:49 🏷  Node name: my-astar
2023-04-06 03:41:49 👤 Role: FULL
2023-04-06 03:41:49 💾 Database: RocksDb at /data/chains/shibuya/db/full
2023-04-06 03:41:49 ⛓  Native runtime: shibuya-95 (shibuya-0.tx2.au1)
2023-04-06 03:41:49 Parachain id: Id(1000)
2023-04-06 03:41:49 Parachain Account: 5Ec4AhPZk8STuex8Wsi9TwDtJQxKqzPJRCH7348Xtcs9vZLJ
2023-04-06 03:41:49 Parachain genesis state: 0x0000000000000000000000000000000000000000000000
000000000000000000005573e7afb9b20990e6d69d28e5d21e921130163f323b2552b8050230e716d4b303170a2e7
597b7b7e3d84c05391d139a62b157e78786d8c082f29dcf4c11131400
2023-04-06 03:41:49 Is collating: no
2023-04-06 03:42:10 [Parachain] Found wasm override. version=shibuya-95 (shibuya-0.tx2.au1) f
ile=/var/lib/astar/wasm/shibuya-runtime-95-substitute-tracing.wasm
2023-04-06 03:43:47 [Relaychain] 🏷  Local node identity is: 12D3KooWGVCjPKZeUzV3wt9saXbqBFDQ7
bUNAuVmxkDCMTFHNGen

Expected vs. Actual Behavior

When I run debug_traceTransaction, it returns the following

❯ curl -H 'Content-Type: application/json;charset=utf-8' --data '{"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xc60b6253d9e1051e94c0a8de5e51c8b43441279388393a988204a832b8ccf875"],"id":1129}' localhost:9933
{"jsonrpc":"2.0","error":{"code":-32603,"message":"Runtime api version call failed (trace)"},"id":1129}%

Environment

• Project version/tag: v5.3.0
• Runtime: shibuya-runtime-95-substitute-tracing.wasm

[akru]

Hello, current Shibuya runtime spec is 92, in your example used spec 95 override. Unfortunately it will not work until Shibuya get upgraded. Please wait a bit.