docs: Gaia v14 upgrade hermes update (#2854)

* Updated v14 migration information with relayer information

* Removed ICS goto market doc

* Added ICS docs

docs/getting-started/system-requirements.md

@@ -1,7 +1,15 @@
 
 # System requirements
 
-The Gaia application typically needs at least 32GB RAM for smooth operation.
+<!-- 
+## Validator Nodes
+
+## Archive Nodes 
+-->
+
+## Gaia Upgrades
+
+The Gaia application typically needs at least 32GB RAM, for smooth operation for upgrade, as there may be lenghty migrations to perform.
 
 If you have less than 32GB RAM, you might try creating a swapfile to swap an idle program onto the hard disk to free up memory. This can allow your machine to run the binary than it could run in RAM alone.
 

docs/interchain-security/README.md

@@ -0,0 +1,11 @@
+---
+order: false
+parent:
+  order: 2
+---
+
+# Interchain Security
+
+This folder contains an overview of Interchain Security, one of the core features of the Cosmos Hub.
+
+- [Interchain Security](./interchain-security.md)

docs/interchain-security/interchain-security.md

@@ -0,0 +1,22 @@
+---
+order: 5
+title: Introduction to Interchain Security
+---
+
+# Interchain Security
+
+The Interchain Security feature, brings to the Cosmos Hub a shared security model, where the Cosmos Hub validators, also validate on consumer chains. This is valuable for consumer chains, as consumer chains can focus on product-market fit, rather than business and operational agreements in bringing together a validator set. As part of this agreement, consumer chains pay for the security by distributing a portion of the consumer chain revenue to Hub token holders.
+
+All potential chains are onboarded as consumer chains, via Hub Governance, with the feedback from the Hub community.
+
+Currently the Cosmos Hub has the following two Consumer Chains.
+
+## Neutron
+
+[Neutron](https://neutron.org/), is a smart contracting platform, that was the first consumer chain onboarded.  
+Neutron was onboarded as a consumer chain in May 2023, see Hub [proposal 792](https://www.mintscan.io/cosmos/proposals/792) for more details.
+
+## Stride
+
+[Stride](https://www.stride.zone/), is a liquid staking provider, which aims to unlock liquidity for Cosmos Hub token holders.  
+Stride was onboarded as a consumer chain in July 2023, see Hub [proposal 799](https://www.mintscan.io/cosmos/proposals/799) for more details.

docs/migration/cosmoshub-4-v14-upgrade.md

@@ -5,10 +5,12 @@ order: 8
 <!-- markdown-link-check-disable -->
 # Cosmos Hub 4, Gaia v14 Upgrade, Instructions
 
-This document describes the steps for validators and full node operators, to upgrade successfully to the Gaia v14 release.
+This document describes the steps for validators, full node operators and relayer operators, to upgrade successfully for the Gaia v14 release.
 
 For more details on the release, please see the [release notes](https://github.com/cosmos/gaia/releases/tag/v14.1.0)
 
+**Relayer Operators** for the Cosmos Hub and consumer chains, will also need to update to use [Hermes 1.7.3](https://github.com/informalsystems/hermes/releases/tag/v1.7.3) or higher, see [Relayer Operations](#relayer-operations) or more details.
+
 ## Release Binary
 
 > Please note that the **v14.0.0** binary is depreceated and **ALL** validators **MUST** use the **v14.1.0** binary instead.
@@ -38,6 +40,7 @@ For more details on the release, please see the [release notes](https://github.c
   - [Rollback plan](#rollback-plan)
   - [Communications](#communications)
   - [Risks](#risks)
+  - [Relayer Operations](#relayer-operations)
   - [Reference](#reference)
 
 ## On-chain governance proposal attains consensus
@@ -203,6 +206,38 @@ As a validator performing the upgrade procedure on your consensus nodes carries
 
 The riskiest thing a validator can do is discover that they made a mistake and repeat the upgrade procedure again during the network startup. If you discover a mistake in the process, the best thing to do is wait for the network to start before correcting it.
 
+## Relayer Operations
+
+The Gaia `v14.1.0` upgrade brings forth the cryptographic verification of equivocation feature from ICS `v2.4.0-lsm`. This important security enhancement empowers external agents to promptly submit evidence evidence of light client and double signing attacks observed on a consumer chain. Operators can seize the control of this feature using either the dedicated ICS CLI commands or unleash the power of the Hermes IBC relayer in “evidence” mode. 
+
+This feature is supported by an updated [Hermes v1.7.3](https://github.com/informalsystems/hermes/releases/tag/v1.7.3).
+
+### **1. Hermes “evidence” mode**
+
+Ensure you have a well-configured Hermes `v1.7.3+` relayer effectively relaying packets between a consumer and a provider chain. The following command demonstrates how to run a Hermes instance in “evidence” mode to detect misbehaviors on a consumer chain.
+
+```sh
+hermes evidence --chain <CONSUMER-CHAIN-ID>
+```
+
+**Tip**: this command takes a `--check-past-blocks` option giving the possibility to look for older evidences (default is `100`).
+
+### **2. ICS CLI**
+
+The ICS provider module offers two commands for submitting evidence of misbehavior originating from a consumer chain. Here are two examples illustrating the process:
+
+To submit evidence of a double-vote:
+
+```sh
+gaiad tx provider submit-consumer-double-voting [path/to/evidence.json] [path/to/infraction_header.json] --from node0 --home ../node0 --chain-id $CID
+```
+
+And for a light client attack:
+
+```sh
+gaiad tx provider submit-consumer-misbehaviour [path/to/misbehaviour.json] --from node0 --home ../node0 --chain-id $CID
+```
+
 ## Reference
 
 [Join Cosmos Hub Mainnet](https://github.com/cosmos/mainnet)