The app can be configured in a number of ways via environment variables. Without any settings, the app is configured to connect to our Rinkeby deployment fetching metadata from a non-local IPFS Gateway.
Expected chain id to connect to. Either one of 1 (mainnnet), 3 (ropsten), 4 (rinkeby) or 1337 (local).
Url of the default Ethereum node to read blockchain data from. If you intend to connect to a local ganache instance, by default you should set this to http://localhost:8545.
Url of the IPFS Gateway to load disputes metadata from. If you intend to connect to a local IPFS daemon's Gateway, by default you should set this to http://localhost:8080/ipfs.
Name of the subgraph instance to connect to and query data from. This is useful when we have different Celeste deployments on the same network.
API key from Formatic. Requires separate keys for testnet / mainnet.
API key from Portis. Requires separate keys for testnet / mainnet.
To disable flagging of voided disputes.
Sentry DSN for forwarding error logs.
To start Celeste dashboard with mocked data.
- Ethereum node: 8545
- Subgraph:
- 8000 (HTTP)
- IPFS Gateway: 8080
- Celeste server: 8050
myth like bonus scare over problem client lizard pioneer submit female collect