Platform modules

Published 15 August 2018

Transactional level

Transactional level

User - The user defines a pair of asymmetric encryption keys that are used to confirm authorship and protect the integrity of information.

Transaction - A transaction is a "count-count-sum" entry. The user's public key is used as the account of the sender and the recipient.

Balance - The sum of all incoming (positive) and outgoing (negative) transactions is a balance. These are the current assets of the user.

Creature To create a transaction, the user needs to have a positive balance.

Verification - Before saving in the main transaction chain, the transaction must be verified by a group of trusted nodes. The amount of the transaction can not exceed the balance (except in special cases, when transactions are executed simultaneously, the overall balance is positive). Transactions are verified by blocks and if necessary, broken into sub-blocks. Details are in the mechanism "algorithm of Byzantine generals."

Recording - Transactions are grouped into blocks that are linked to the common transaction chain by including the hash of the previous block. Protection against changes is provided by hashing and electronic signature of the recording node.

Contracts - A contract is an executable code stored in a database. The contract code can be written to the database and read from it.

Votes 0, average rating 0