You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,10 +59,12 @@ Running the following commands will start a Docker container in
59
59
a data directory at `<working directory>/ethereum-data` and the Rosetta API accessible
60
60
at port `8080`.
61
61
62
-
The `NETWORK` environment variable can be set to `MAINNET`, `ROPSTEN`, `RINKEBY`, `GOERLI` or `TESTNET` (which defaults to `ROPSTEN`).
63
-
64
-
_It is possible to run `rosetta-ethereum` using a remote node by adding
65
-
`-e "GETH=<node url>"` to any online command._
62
+
#### Configuration Environment Variables
63
+
*`MODE` (required) - Determines if Rosetta can make outbound connections. Options: `ONLINE` or `OFFLINE`.
64
+
*`NETWORK` (required) - Ethereum network to launch and/or communicate with. Options: `MAINNET`, `ROPSTEN`, `RINKEBY`, `GOERLI` or `TESTNET` (which defaults to `ROPSTEN` for backwards compatibility).
65
+
*`PORT`(required) - Which port to use for Rosetta.
66
+
*`GETH` (optional) - Point to a remote `geth` node instead of initializing one
67
+
*`SKIP_GETH_ADMIN` (optional, default: `FALSE`) - Instruct Rosetta to not use the `geth``admin` RPC calls. This is typically disabled by hosted blockchain node services.
0 commit comments