Unsynced node causes weird error message

[xianghl01]

when I run chifra blocks 12, the result is

WARN[21-05|18:41:21.249] the --call value provided (manifestHashMap(0x0, "mainnet-ts")) was not found: abi not found for manifestHashMap(0x0, "mainnet-ts"): abi not found 
{
  "data": [],
  "errors": [
    "Post \"http://localhost:8545\": dial tcp 127.0.0.1:8545: connect: connection refused"
  ]
}

what should i do

[Pavel Fedotov]

I have the same issue, It probably stems from not configuring $CONFIG/trueBlocks.toml from installation guide https://trueblocks.io/docs/install/install-core/

[Pavel Fedotov]

Edit the trueBlocks.toml with a provider

[Thomas Jay Rush]

This issue is almost certainly caused by not having properly modified your configuration to point to a valid RPC provider for the Eth mainnet (Eth mainnet is the only required RPC).

You should be able to do this with chifra config edit.

If that doesn't work, edit the trueBlocks.toml file found when you enter chifra config --paths.

Once you're inside the .toml file, find the section called [chains]. Within that section, find a section called [mainnet]. Modify the rpcProvider to point to a valid RPC provider for mainnet Ethereum. (You can search the web for such.)

Another thing to note. In order for the chifra init command to work, your node must be synced to at least block 18,538,072. You will get this message if your node is not at least that far advanced.

You can check how far you're synced with chifra when latest.

[Thomas Jay Rush]

I think this is fixed. A change will come to develop soon (and master soon thereafter). I will close this in the hopes that it's fixed. If not, we can re-open it.