eth_genesis used in gwemix download-genesis is feature for downloading genesis config from gwemix node.
Currently, the API returns content of genesis.json specified on startup.
The API does not reflect default chain config which is set on runtime so actual config is hidden to outside unless attaching IPC.
It may be reasonable as aspect of downloading genesis "file" which node used but most expects downloading "current" genesis.
Moreover, the API does not work when genesis.json is removed from node.
For testnet:
$ curl -H "Content-Type: application/json" \
-d '{"id":0,"jsonrpc":"2.0","method":"eth_genesis","params":[]
}' https://api.test.wemix.com
{"jsonrpc":"2.0","id":0,"error":{"code":-32000,"message":"open /opt/nxt/genesis.json: no such file or directory"}}
For mainnet EN:
$ curl -H "Content-Type: application/json" \
-d '{"id":0,"jsonrpc":"2.0","method":"eth_genesis","params":[]
}' https://api.wemix.com
{"jsonrpc":"2.0","id":0,"error":{"code":-32000,"message":"open /opt/wemix/genesis.json: no such file or directory"}}
eth_genesis
used ingwemix download-genesis
is feature for downloading genesis config from gwemix node. Currently, the API returns content of genesis.json specified on startup. The API does not reflect default chain config which is set on runtime so actual config is hidden to outside unless attaching IPC. It may be reasonable as aspect of downloading genesis "file" which node used but most expects downloading "current" genesis.Moreover, the API does not work when genesis.json is removed from node.
For testnet:
For mainnet EN: