In general, Stegano follows the philosophical approach of the scalable, geo-replicated, transactional datastore CockroachDB or Google's scalable, multi-version, globally-distributed, and synchronously-replicated database, Spanner ... except that the aim of Stegano is build things that will serve as key components of a highly-available fault-tolerant trust network and messaging system for accelerated negotiation/auction.
The steganographic blockchain eventually strong "auctioneering" consensus algorithms will push Stegano to be significantly fuzzier and maybe even more distributed and more lightweight than general-purpose datastores like Cockroach which tend to rely on the highly-understandable Raft or a variant like Ark. Relying on the specific attributes of the transactions allows for an "election" to rely upon Paxos or Chandra-Toueg derivatives or an auctioneered consensus algorrithm that is not intended for general use. The FUZZINESS of the steganographic blockchain eventually strong "auctioneering" consensus algorithms will rely upon zero-shot machine learning perhaps with convex combination of semantic embeddings or a supervised deep semantic embedding to "auctioneer" or lead a consensus between different competing bid/ask offers.
The Stegano.FARM project that utilizes the Elixir and Erlang OTP approach to spawn very lightweight nanoprocesses which are the basis of massively scalable soft highly available real-time systems used in telecom, banking, e-commerce, computer telephony and instant messaging.
The Stegano algorithmic strategy is basically a "divide-and-divide-and-divide-and-divide-some-more-and-then-conquer-and-digest-and-rebuid" approach folloing the Industry-Farm-Pig-Microbe-Nutrient paradigm or metaphor we see in nature or agriculture ... the trust network (Industry) builds an "eventually strong" Chandra-Toueg consensus using a distributed set of macro processors (Farms) that raise and tend many spawned processes (Pigs) that each rely upon many spawned microprocesses (Microbes) which digest and feed upon an almost infinite number of nanoprocesses (Nutrients).
Datastore architecture drives language and consensus algorithm approach which would be another reason that Stegano is not a fork of the CockroachDB repository. The primary reason is that CockroachDB is an exciting project and merits focus of DevOps engineers working in this realm. We strongly urge interested parties to try, use follow and join us in contributing to CockroachDB.