Supernodes check delivered blocks from micronodes and macronodes and confirm them sequentially. If an incorrect block is delivered, supernodes reject the block.
Supernodes record the results of micronodes and macronodes voting on the block generation.
Supernodes keep all transactions occurring in the network in a form of block.
Supernodes provide the Dapp source file storage space. Source files are stored off-chain.
Files that individual supernodes store are determined by selected supernodes. In this process, a matter of choice does not exist as compensation is ditributed in proportion to the storage capacity unit. (See the supernode source file storage)
Supernodes provide their source files to micronodes when the micronodes require them.
Supernodes provide source files to macronodes to execute the source files.
Selected supernodes regularly confirm what macronode should execute what sourcefile based on the execution frequency of source files and the macronode compensation data, and regularly provide the source files according to this process. (See the selected supernode)
When supernodes are requested to execute source files, they route the requests to macronodes possessed the source files.
Supernodes randomly choose nodes to verify transactions of micronodes at regular intervals. (See the GBT transaction verification mechanism)
Supernodes arrange transactions occuring from micronodes and spread them to the selected verification pool.
Selected supernodes check the online and offline status of individual micronodes to generate the verification pool. (See the selected supernode)
Supernodes verify contracts in the GBT Protocol other than GBT transactions and SC transactions. (See the GBT Protocol contract verification mechanism)
Supernodes should be verified that they have the server-level infrastructure through the GBT Protocol client.
To participate as a supernode, participants should stake minimum k tokens.
The amount of Staking ① guarantees faithful behaviors of supernodes, which is ② smaller than the amount of Staking by macronodes, ③ and is set equal to the same level by supernode considering the entry barrier.
The amount of Staking is in proportion to the source file storage space that will be provided by supernodes. It is becausethe more storage space is provided, the bigger responsibility follows.
The amount of tokens to be staked per storage space is determined by supernodes’ voting on a basis of Fiat. The amount is regularly renewed.
In case of renewal, original participants are not affected by th changed amount of Staking. However, in case of re-Staking after punishment or new participation in the new network, the original participants follow the renewed amount of Staking.The more tokens are staked, the bigger storage space that supernodes can provide is.
Supernodes receive fees from Dapp source file developers for storing files. (See the supernode source file storage)
Supernodes receive fees from developers for compensation for providing source files to micronodes. (See the supernode source file storage)
Supernodes are punished for not providing source files requested by micronodes and macronodes. (See the supernode source file storage)
Supernodes are punished if the compensation variability for macronodes executing their source files is over a certain standard. The standard of compensation variability is the standard deviation.
In case of the verification value not submimited or the incorrect verification value submitted, n% of a supernode’s Staking are deducted. In this case, supernodes cannot get compensation for the relevant verification.
Punished supernodes should stake more tokens to cover insufficient amounts of the storage space previously occupied.
Server-level or higher level infrastructure companies