chore: add config example

QuokkaStake · Dec 23, 2023 · 45be084 · 45be084
1 parent 42f81d6
commit 45be084
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 1 deletion.
diff --git a/README.md b/README.md
@@ -109,7 +109,7 @@ Go to your PagerDuty page, then go to Services. Create a service if you haven't
 
 ## Which networks this is guaranteed to work?
 
-In theory, it should work on a Cosmos-based blockchains that expose a REST server.
+In theory, it should work on a Cosmos-based blockchains that expose a REST server, and also on Neutron.
 
 ## How can I contribute?
 

diff --git a/config.example.toml b/config.example.toml
@@ -39,6 +39,12 @@ wallets = [
     { address = "bitsong14rvn7anf22e00vj5x3al4w50ns78s7n4t8yxcy", alias = "Validator wallet" },
     { address = "bitsong125hdkukw4pu2urhj4nv366q0avdqv24t0vprxs" },
 ]
+# Type. Currently can be either "cosmos" or "neutron". Optional, defaults to "cosmos.
+type = "cosmos"
+# Neutron smart contract address. Defaults to "neutron1436kxs0w2es6xlqpp9rd35e3d0cjnw4sv8j3a7483sgks29jqwgshlt6zh"
+# (mainnet contract address).
+neutron-smart-contract = "neutron1436kxs0w2es6xlqpp9rd35e3d0cjnw4sv8j3a7483sgks29jqwgshlt6zh"
+
 # Some chains have a new proposals structure (v1) compared to an older one (v1beta1),
 # when there are 2 or more actual proposals inside a single one (namely, Quicksilver).
 # On such chains, querying proposals with an older endpoint when there are proposals