Timeline for Using jsonrpc to get eth data but the result is null
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2018 at 4:52 | comment | added | Ismael♦ | Is your node fully synced? A node syncing in fast mode will not return meaningful data until it has finished (ethereum.stackexchange.com/questions/24667/…). | |
| Apr 4, 2018 at 4:50 | history | edited | Ismael♦ | CC BY-SA 3.0 |
Formatting
|
| Apr 3, 2018 at 6:35 | comment | added | Denver Jacob | curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}' localhost:8545 -H 'content-type: application/json' and the output is {"jsonrpc":"2.0","id":83,"result":"0x0"} I have downloaded all the blocks, the result should not be 0 | |
| Apr 3, 2018 at 6:32 | comment | added | user19510 | You said you get a "null" result, but you don't. You get a JSON response with the correct ID and the result 0. I assume that this is because the current block number on the node you're connecting to is 0. | |
| Apr 3, 2018 at 6:29 | comment | added | Itération 122442 | Can you post the code here (in text), I can't access the image from where I am. | |
| Apr 3, 2018 at 6:28 | history | asked | Denver Jacob | CC BY-SA 3.0 |