From 7000acc4caac1febe6c125cd1dbf2c4336a7197c Mon Sep 17 00:00:00 2001
From: a10zn8 <a1.cyb3r@gmail.com>
Date: Wed, 1 Feb 2023 19:31:03 +0400
Subject: [PATCH] added all chain types to docs

---
 docs/04-upstream-config.adoc | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/04-upstream-config.adoc b/docs/04-upstream-config.adoc
index 00af1a47..c749fc90 100644
--- a/docs/04-upstream-config.adoc
+++ b/docs/04-upstream-config.adoc
@@ -122,6 +122,23 @@ In the example above we have:
 
 *It's kindly recommended* to strictly associate _node-id_ parameter with a physical node and keep it during any configuration changes
 
+=== Supported chains
+
+Currently, dshackle supports next chains (should be used as chain names in config):
+
+- ethereum (eth)
+- ethereum-classic (etc)
+- polygon (matic)
+- arbitrum (arb)
+- optimism
+- binance (bsc, bnb-smart-chain)
+- morden
+- kovan (kovan-testnet)
+- goerli (goerli-testnet)
+- rinkeby (rinkeby-testnet)
+- ropsten (ropsten-testnet)
+- bitcoin (bitcoin-testnet)
+
 === Roles and Fallback upstream
 
 By default, the Dshackle connects to each upstream in a Round-Robin basis, i.e. sequentially one by one.