This is useful. I also suggest using the Diamond Standard. With the Diamond Standard you can deploy small proxy contracts that can reuse many different on-chain logic/facet contracts. This gives a lot of flexibility while saving deployment gas. The standard is here: https://eips.ethereum.org/E...

I was intrigued by this clone factory pattern, until I read this:

What if the library address contract self-destructs?

All previously deployed contracts would stop working, so make sure this cannot happen.

In complex smart contact systems, this kind of irreversible process would better be avoided. It's bad when bugs are found in just one contract, but an unintended self-destruct of a library that's the backbone of many other clone contracts? That'd be shitshow!

Yeah, it's called "Parity".

This is a great article, thank you!