Open jerryleooo opened 1 year ago
Did you use pokt's "Ethereum Mainnet Archival with trace calls" as described in the readme? trace_block
isn't enabled for most eth endpoints by default.
Hello, I'm having the same issue, even though I'm using the right pokt's endpoint: https://eth-trace.gateway.pokt.network/v1/lb/<id>
I'm still getting error messages such as the method trace_block does not exist/is not available
or the method eth_getBlockReceipts does not exist/is not available
I can successfully get the result simply by repeating the command ./mev inspect <block number>
several times.
Having the same issue. Did anyone manage to solve this?
I did not resolve this issue; it appears that the endpoint is busy; it will return an error under high workload.
I write a script that calls the endpoint repeatedly until it returns without error. It output the error message to call_endpoint.log
, If there is no error log, it will request the next block number.
#!/bin/bash
START=<start_block_number>
END=<end_block_number>
for i in $(eval echo "{$START..$END}"); do
until [ ! -s ./call_endpoint.log ]; do
./mev-inspect-py/mev inspect $i 2>./call_endpoint.log
sleep 1
done
echo "task finished" >> ./call_endpoint.log
done
same problem
Why isn't it fixed? I used pokt's archival node. However, I still encounter this error.
Common RPC node service providers, such as Infura/alchemy, generally do not open this method
I have investgated and spoken to POKT about this issue.
Pokt as a network aims to be node-agnostic; and it is unable to tell which calls are Erigon specific. Hence, any Erigon-specific calls are sometimes sent to Erigon, but other times sent to a Geth node (in which case, they fail with the errors above).
This issue imo requires changing the docs to reccomend a different RPC rather than any code changes.
I have tested an ANKR RPC, which is working as expected.
I am using an endpoint from pokt.network:
https://eth-mainnet.gateway.pokt.network/v1/lb/xxxx
I have done all steps mentioned in the README, while got following error: