The evolution of the transition to Trusted HW

Greetings, dear readers of the blog! In today’s article we are talking about the evolution of the transition to Trusted Hardware. Let us tell you about the canonical hierarchy of modularity and dialectics in GONT, let’s talk about the implementation at the SW and HW levels and touch upon the topic of verifiers.

General course on Trusted Hardware

Trusted HW – Trusted Hardware.

It should be noted that the consensus may be different:
PoW, PoS, ProgPow, alternate (like FileCoin), etc.

But the general course on Trusted Hardware (GONT processor consensus!) will radically change the blockchain industry!

Canonical modularity hierarchy in GONT and dialectic

For a long-term and sustainable self-development system, it is necessary to initially lay down a hierarchy of complexity. The system cannot be qualitatively improved simply by linear growth and scaling.

The most difficult levels of technology (SuperKANT) should dialectically “pull out” the development of simple modules (Oracle and gVM).

The initial (canonical) hierarchy of modularity sets the possibilities for many non-trivial growth scenarios for the entire system. And this makes it possible to build a nontrivial (crypto) economy of GONT. Much more advanced than just tokenomics.

Table. Evolution of the complication of GONT entities.

GPNP – pre-processing of packet data on the fly, in close proximity to the gVM calculator. From here comes the core of GOYA with GPNP architecture.

Read more about GPNP in the article GONT 3G: GOYA, GPNP and GONT.Agent.

Hierarchy structure for integrity

Ontologies are needed not only to describe both open and confirmed meanings, but also to realize the integrity of the entire system.

Hierarchy and module independence

  • Oracle (1)
  • gVM (2)
  • KANT (3)
  • SuperKANT (4)

A module of a higher hierarchy can check the integrity of nested modules (4), etc.

Implementation at SW and HW levels

To fully implement the secure AlGas concept, an evolution to trusted hardware is required.


The entire system as well as the trusted hardware blocks must at any time be independently verifiable.

For example, one global bug in Intel chips could bring down the entire Ethereum blockchain. But the whole community (in consensus) believes that Intel chips are perfect and you can build the whole system on them. Although theoretically it is not.

Verifiers are separate blocks through which anyone can independently verify trusted hardware for functional equivalence of a software (theoretical) model.

Thank you for attention! See you next week.

Leave a Reply