mdbx: update MithrilDB status (backport).

README.md

@@ -81,19 +81,48 @@ Historically, _libmdbx_ is a deeply revised and extended descendant of the amazi
 [Lightning Memory-Mapped Database](https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database).
 _libmdbx_ inherits all benefits from _LMDB_, but resolves some issues and adds [a set of improvements](#improvements-beyond-lmdb).
 
+### MithrilDB and Future
+
 <!-- section-begin mithril -->
 
-The next version is under active non-public development from scratch and will be
+The next version is under non-public development from scratch and will be
 released as **MithrilDB** and `libmithrildb` for libraries & packages.
 Admittedly mythical [Mithril](https://en.wikipedia.org/wiki/Mithril) is
 resembling silver but being stronger and lighter than steel. Therefore
 _MithrilDB_ is a rightly relevant name.
 
-   > _MithrilDB_ will be radically different from _libmdbx_ by the new
+_MithrilDB_ is radically different from _libmdbx_ by the new database
-   > database format and API based on C++17, as well as the [Apache 2.0
+format and API based on C++20. The goal of this revolution is to provide
-   > License](https://www.apache.org/licenses/LICENSE-2.0). The goal of this
+a clearer and robust API, add more features and new valuable properties
-   > revolution is to provide a clearer and robust API, add more features and
+of the database. All fundamental architectural problems of libmdbx/LMDB
-   > new valuable properties of the database.
+have been solved there, but now the active development has been
+suspended for top-three reasons:
+
+1. For now _libmdbx_ «mostly» enough for all [our products](https://www.ptsecurity.com/ww-en/products/),
+and I’m busy in development of replication for scalability.
+2. Waiting for fresh [Elbrus CPU](https://wiki.elbrus.ru/) of [e2k architecture](https://en.wikipedia.org/wiki/Elbrus_2000),
+especially with hardware acceleration of [Streebog](https://en.wikipedia.org/wiki/Streebog) and
+[Kuznyechik](https://en.wikipedia.org/wiki/Kuznyechik), which are required for Merkle tree, etc.
+3. The expectation of needs and opportunities due to the wide use of NVDIMM (aka persistent memory),
+modern NVMe and [Ангара](https://ru.wikipedia.org/wiki/Ангара_(интерконнект)).
+
+However, _MithrilDB_ will not be available for countries unfriendly to
+Russia (i.e. acceded the sanctions, devil adepts and/or NATO). But it is
+not yet known whether such restriction will be implemented only through
+a license and support, either the source code will not be open at all.
+Basically we are not inclined to allow our work to contribute to the
+profit that goes to weapons that kill our relatives and friends.
+NO OPTIONS.
+
+Nonetheless, I try not to make any promises regarding _MithrilDB_ until release.
+
+Contrary to _MithrilDB_, _libmdbx_ will forever free and open source.
+Moreover with high-quality support whenever possible. Tu deviens
+responsable pour toujours de ce que tu as apprivois. So we will continue
+to comply with the original open license and the principles of
+constructive cooperation, in spite of outright Github sabotage and
+sanctions. I will also try to keep (not drop) Windows support, despite
+it is an unused obsolete technology for us.
 
 <!-- section-end -->
 

docs/_toc.md

@@ -38,4 +38,4 @@ including creating [merge-request](https://gitflic.ru/project/erthink/libmdbx/me
 
 ---
 
-\section MithrilDB MithrilDB
+\section MithrilDB MithrilDB and Future