Thorchain hardfork preparation

In about two weeks THORChain will hard fork, so integrating projects need to be aware that:

If a project supports sending (MsgSend) or depositing (MsgDeposit) RUNE, synths, or trade assets the chain-id will need to be updated to support the new chain (details below)
There will be planned downtime of all THORChain services and transactions including transferring rune, swapping, savers, lending, thorname, and node operations. Exact timing of the downtime is to be determined and will be communicated once decided.

Projects that support any type of transaction of the THORChain network are advised to immediately start pulling in THORChain’s current chain-id dynamically in transaction creation to ensure no service interruptions occur after the chain is hard fork.
Use the following endpoint: https://rpc.ninerealms.com/status
Retrieve the current chain-id from the result.network property
Use this chain id when building all THORChain transactions
After the hard fork, this value will automatically update with the new chain id

Ensure your interface is not allowing any swaps, savers actions, lending actions, rune transfers, or any other network operation during the planned downtime.
If your interface is using the quote endpoint ensure no swaps are sent if you receive an error from that endpoint or if the endpoint is not available

update chain id in all applicable txs - rune classic transactions should also use the new chainId to ensure they can be looked up by new accountId which will be using the new chainId (everything should act is if they are the same chain)
confirm graceful failure state for app during plan downtime (double check swapper, TC defi, and that we show an intelligible state to users)

shapeshift / web