This page documents setting blockchain types and endpoints for the tools.
The tools support the following arguments.
--blockchain BLOCKCHAIN- the type of blockchain to connect to. See below for supported blockchains.--api-url API_URL- URL of RPC API of the corresponding fullnode, for example:--api-url http://127.0.0.1:8332/. Note that every blockchain type sets sensible default for API_URL, using127.0.0.1and appropriate port, so specifying--api-urlmanually may be unnecessary.--api-url-username API_URL_USERNAME,--api-url-password API_URL_PASSWORD- allows to set username and password for HTTP authentication for the endpoint.--api-url-insecure- disable validation of HTTPS certificates (if URL is HTTPS).
| Blockchain | --blockchain |
|---|---|
| Binance Chain | binance |
| Bitcoin | bitcoin |
| Cardano | cardano |
| Cosmos | cosmos |
| EOS | eos |
| EOS with history plugin | eos_archive |
| Ethereum | ethereum |
| Grin | grin |
| Monero | monero |
| NEM | nem |
| NEO | neo |
| Ripple | ripple |
| Stellar | stellar |
| Generic Tendermint | tendermint |
| Tezos | tezos |
| Tron (WIP) | tron |
| Waves | waves |
Most forks of Bitcoin (using the same RPC API) can be exported using bitcoin blockchain type. You only need to specify correct port and host with --api-url, because default is set for Bitcoin Core (http://127.0.0.1:8332/).
Username and password for RPC API can be set with --api-url-username and --api-url-password options.
Tested only with Ethereum Parity. Works with both Ethereum and Ethereum Classic.
If your Parity node records tracing information, you can specify --trace to include it in exported output.
eos is for normal EOS RPC API. eos_archive is for exporting data from State History Plugin. Output data format of eos and eos_archive is very different.
Ripple mode requires history server, not fullnode. By default it uses official history server.
Stellar mode requires history server, not fullnode. By default it uses official history servers.