As an SPO and the main contributor to the CoinCashew guide, the following fundamental issues and gaps in Mithril documentation make the decision to adopt and support Mithril difficult:

1. Mithril remains in beta.
2. When a new version of Cardano Node is installed, what maintenance or administrative procedures may Mithril Signer require to continue operating successfully?
3. In a stake pool configuration, when the blockchain on all Cardano Node instances operating as relay nodes is restored using Mithril Client to retrieve a snapshot, what is the procedure or recommended practice for restoring the blockchain on the block producer if needed? In such a scenario, must the block producer use Mithril Client to restore the blockchain as well? If so, does Mithril Client support retrieving an available snapshot from one of the connected relay nodes? Or, must the block producer now break security protocols to bypass the relay nodes and connect Mithril Client directly to the Internet in order to retrieve a snapshot? What may be the recommendations for implementing Mithril Client in a stake pool configuration?

Consider the incentives for a moment. Implementing Mithril Signer creates a down side of increasing the ongoing administrative responsibilities for an SPO. However, using Mithril Client potentially offsets the additional work by significantly reducing the amount of time and complexity involved in restoring the blockchain, when needed. Implementing Mithril Signer without Mithril Client may not incentivize individual SPOs enough to install Mithril.

Developing some use cases in Mithril documentation presenting recommended or best practices for SPOs to implement Mithril may be helpful and necessary for Mithril to gain enough mainnet adoption to support an official launch.