I wrote this on x / twitter this morning, thought some here would find interesting...

Several questions have arisen regarding the operation of your mercurylayer / Statechain server instance. These inquiries became more frequent then during the development of MercuryWallet, but this time, there appears to be a genuine interest. To clarify, everything we have developed for mercurylayer is entirely open source, including the HSM component. This component is an open-source implementation on Intel SGX, which means it may not be central to this discussion. Nevertheless, based on the feedback received, we are considering the creation of Docker containers to simplify the process for others.

A few thoughts on this matter: Not all Statechain entities are created equal, just as not all sidechains or Lightning nodes are identical. If a network of Statechain entities were to emerge over time, some form of reputation system might be necessary. Additionally, UTXOs (Unspent Transaction Outputs) among different Statechain servers are not uniform therefore not fungeable. However, this disparity does not prevent the development of a swap service between Statechain UTXOs, which could potentially include Lightning channels. Such a service might help address the liquidity inefficiency in the Lightning Network.

We are always open to further discussions on this topic. Exploring how a mesh network of Statechain entities could interface with Lightning Network Service Providers (LSPs) is intriguing, as it opens up new possibilities.