hi.. i did not receive my transaction to eth network... https://blockscout.com/poa/xdai/tx/0xf995df3bc8cb027b15e6420231f15cbbf794b4b288d3a7d72c9fbfcf8db37d80/internal-transactions
Can someone help me?
[Victor Baranov, POA Network] @ssandeep Blockscout provides catchup fetcher which periodically checks missing blocks in the chain and fetches them eventually. You don’t need to undertake extra steps.
@dannygkass all available API endpoints are listed at /api-docs page. ?module=token especially for token. Also, there are some token related endpoints in ?module=*account* section. If you feel lack of some endpoints, please, create a feature request in the Github repository.
1 reply
```[340]: Retrying.
[340]: 2020-10-14T07:10:49.805 application=indexer fetcher=block_catchup first_block_number=4750082 last_block_number=4750073 [error] ** (MatchError) no match of right hand side value: {:error, {:more, {:hparse
r, :response, 4096, 10, 0, :on_trailers, "", {1, 1}, "", [], :undefined, "chunked", "", "application/json", "", :done}}}
[340]: (indexer 0.1.0) lib/indexer/transform/address_coin_balances_daily.ex:67: anonymous fn/3 in Indexer.Transform.AddressCoinBalancesDaily.reducer/2
[340]: (elixir 1.10.3) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
[340]: (indexer 0.1.0) lib/indexer/transform/address_coin_balances_daily.ex:66: Indexer.Transform.AddressCoinBalancesDaily.reducer/2
[340]: (stdlib 3.12.1) maps.erl:232: :maps.fold_1/3
[340]: (indexer 0.1.0) lib/indexer/block/fetcher.ex:165: Indexer.Block.Fetcher.fetch_and_import_range/2
[340]: (indexer 0.1.0) lib/indexer/block/catchup/fetcher.ex:194: Indexer.Block.Catchup.Fetcher.fetch_and_import_range_from_sequence/3
[340]: (elixir 1.10.3) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2
[340]: (elixir 1.10.3) lib/task/supervised.ex:35: Task.Supervised.reply/5
[340]: Retrying.
2020-10-21T08:48:36.309 application=indexer fetcher=block_catchup first_block_number=5429631 last_block_number=5429631 step=blocks [error] failed to fetch: {:more, {:hparser, :response, 4096, 10, 0, :on_trailers, "", {1, 1}, "", [], :undefined, "chunked", "", "application/json", "", :done}}. Retrying.
This has been fixed in v3.3.3
[Victor Baranov, POA Network] > i see the log, first_block= 11262155 , last_block= 11262146, so the range is only 9 blocks.
Yes, the default batch size for catchup fetcher is 10 blocks. If more blocks are absent then it will be processed in different batches.
and i don’t know why first_block > last_block. is it normal?
that is fine. Blocks will be processed in this range.
Are these params for Geth? Looks good to me. You can check yourself too https://docs.blockscout.com/for-developers/information-and-settings/client-settings-parity-geth-ganache
Why api method "getblockreward" not working? http://explorer.energyweb.org/api?module=block&action=getblockreward&blockno=any_num
Result: {"status":"0","result":null,"message":"Something went wrong."}
[Victor Baranov, POA Network] Hi, in order to make this API endpoint working, Blockscout instance owner should set CHAIN_SPEC_PATH env variable which is
Chain specification path (absolute file system path or URL) to import block emission reward ranges and genesis account balances from. Geth- and OpenEthereum-style specs are supported.
After setting it, the internal process will parse spec file and fetch block reward value into the table. After that, blockreward endpoint should work fine.
The reference to the list of supported ENV vars:
https://docs.blockscout.com/for-developers/information-and-settings/env-variables
[Victor Baranov, POA Network] > the first of all they can not parse my genesis json file
Blockscout supports import from genesis json file for Geth and OpenEthereum archive nodes only. Possibly, format of your JSON file is slightly different. Please open an issue in a Github.
During the syncing I have looked at the node which requests got and i have discovered that the explorer requesting many blocks with almost random block number again and again
Blockscout requests the same data again if the previous try failed. It will continue until the response is successful. Especially at the time of the first syncing, it is recommended to strengthen the node because, indeed, Blockscout performs many requests in order to index chain for the first time.
