Hello everyone! In this article we are talking about the classification of GONT Tree oracle nodes. We will tell you about possible types of “knots”, how they function and also about their further development. Have a productive reading!
What is node?
You can find different interpretations of this concept on the Internet. Node is usually explained as any computer connected to the network.
However, the NODE in GONT is rather the so-called Oracle “knot”, which describes one small part of the virtual machine.
Theory and mechanics of the node in GONT
In the process of implementing chains of values (“Value chains”) of services, several types of nodes can be distinguished. We call this the basic classification.
In fact, we represent any service as a “transaction path” on the GONT Tree. This path is considered to be a chain of creation ща additional service cost (Value Chain).
The possible types of nodes are:
1) Node-S (Node-Service)
Node for “entering” a transaction into a service. From this “node” begins the execution of the service chain. At the same time, it should be noted that a lot of services can be started from one node on GONT Tree. Other users get the right to use any node on GONT Tree to build their services, thereby giving this “knot” the opportunity to earn through the mechanism of AlGas.
2) Node-A (Node-Action)
It is a transaction, the record of which does not occur in the blockchain. The update of the blockchain state is not performed at the time of this transaction. The service provider decides whether to record the transaction in the blockchain or not. However, the execution of this transaction entails consumption of AlGas gas in gVM.
3) Node-B (Node-Baction)
It is a transaction that changes the state of the blockchain. At the moment when the transaction passes the node BAction, it is executed as a normal consensual blockchain transaction.
There are several types of Node-B:
- Starting. Here the transaction starts. In fact, this is Node-S.
- Anadromous. The transaction enters the Node and goes further, thereby changing the state of the BC.
- Closing. Here the service ends and the transaction comes to an end.
What is the fundamental difference between GONT and the basic Ethereum code in implementing the mechanics of the transaction?
It’s easy to see that with respect to the basic Ethereum, where the conditional service “owns” one account and one smart contract “stitched” into the State of this account, GONT has a new set of entities that correspond to the same service.
Minimum one Node-S corresponds to the GONT service. Maximum – an unlimited chain of Nodes. In this case, each node carries semantics of transactions.
How do I build a contract account in Ethereum to Node-S (the start node of the service on GONT Tree)? A smart contract account in Ethereum must “know” with which gVM in the GONT VM pool to start the inbound transaction. This is the first main difference!
Further development of NODE-S and layers
How to describe digital values (arbitrary digital assets)?
Any values are described by templates on GONT Tree.
Let’s introduce the concept of LDA – Layer of Digital Assets. An LDA layer can be attached to any node on the GONT Tree.
Hierarchy can also exist within a LDA layer. For example, by type of container and contract. All this is described (with confirmation) on the GONT Tree.
The data container, in fact, is a reference to a separate nested ontology that describes the data structure. Any “touch of data” in the data container can be a transaction (AlGas) with a unique GONT address of this data. Any contact of data at the address of this data leads to the flow of AlGas gas from the calling party.
Visualization of the hierarchy LDA-Contracts
When the “NODE A” command is called, the execution contracts of this node are also called in any number and sequence.
Thank you for attention! See you in the next articles.