EVM Network works on Subgraph but not on Ponder

[RafaDSan]

The Kakarot network is working to solve its RPC problems, and now the issue mentioned below has been solved.

Also, we are testing fetching the events on the Kakarot network with the Subgraph as well, and the Subgraph correctly fetched the events in the Kakarot network (prints below).

What info can I provide to you to help us debug this problem and to fetch the events in the Kakarot network using Ponder?

@kyscott18 started working on a reproduction here, and found another Kakarot RPC bug.

It looks like EIP-234 eth_getLogs requests return all logs on the chain, regardless of which block they were emitted in. Can reproduce with this request:

curl -X POST -H "Content-Type: application/json" --data '{
    "jsonrpc": "2.0",
    "method": "eth_getLogs",
    "params": [{
        "blockHash": "0x020dc933dc5772707a9b78f76010b2c538d3e55423646481ccefa56ae0a7e887"
    }],
    "id": 1
}' https://sepolia-rpc.kakarot.org

We work hard to triage, reproduce, and fix every bug report that we receive. It’s time-consuming work. Unfortunately, after two incidents of non-compliance, we can’t accept bug reports for apps using Kakarot until we see evidence that they are thoroughly testing their RPC (related issue).

Closing for now. There may indeed be a Ponder bug here, and we will gladly revisit once the Kakarot RPC test coverage has improved.

Endpoint running GraphQL queries returning the events emitted on the Kakarot network

Kakarot scan showing emitted events of swaps created

Related issue:

#886

Update

The number of events displayed in the log are showing correctly now (print 1), but still no return in the endpoint graphql(print2)

(print1)

(print2)

[swetshaw]

Hello @RafaDSan , I am from Kakarot team. Tried reproducing the issue using this repo. But able to get the events when using the same query with the graphql endpoint.

Using Ponder version 0.4.40

We can mark this issue closed

[RafaDSan]

Thank you for your time and feedback on this issue, @swetshaw! I'll close the issue as it's working correctly.