Oil Gas Token: is a general ledger based on blockchain not controlled by a central authority.
This general register writes encrypted data that is shared between the nodes of the network that participate in the process, is validated by the network itself and composed of traced, immutable and highly secure transactions.
Anyone in the chain has a copy of the entire process and certifies the truth, it is technically not possible for one link in the chain to manipulate other data.
Oil Gas Token is a blockchain-based ledger that will receive data mainly from the Oil Gas Token website, but it is an expandable solution based on microservices capable of receiving traceability data from various sources such as mobile apps, IoT (Internet of Things).
The solution can be adapted for specific needs and is scalable to offer a large number of transactions every day.
A blockchain is an append-only structure: you can only add new data, there is no way to change or modify: If something has been registered with incorrect data, it is required to act as on the old ledger, ie a new one accounting reversal recording.
From the developer's point of view it is possible to query a blockchain only with a forward-only approach (forward only), it is necessary to perform a line-by-line scan of the chain, it is not possible to query the chain with relational operators and therefore a scan must be performed line by line, isolate the elements that correspond to the query, save them on an intermediate structure and then present the result: this could be a very burdensome process.
Oil Gas Token has an innovative structure that allows the benefits of a blockchain combined with the versatility and speed of a relational database.
HOW IT WORKS
In Oil Gas Token the blockchain is called only when data is entered, since the data is simultaneously inserted into a relational database.
Every other Oil Gas Token operation is then performed using the database, which allows complex queries and data aggregations.
Each operation is monitored and recorded in log files, with a dedicated web interface for monitoring and alerts.
In the solution we are creating the security has many layers, starting from the user autentication:
The authentication uses the normal user password approach but also a supplementar security layer based on Google Authenticator.
The main archives are Users with renewables (we are seeing initial mockups):
Users with buffers:
Every step can be tracked by a QRcode: