The Clusterstamp has been deployed into the COTI Network — making COTI’s network lighter, faster, and more secure
COTI has developed a new approach to achieving consensus between transacting parties operating on a DAG-based data structure. The Cluster is a ledger, or a record of all transactions in the network, that is based on a completely decentralised DAG that is not stored by any central authority. The Cluster achieves scalability through its use of parallel source selections and transaction confirmations, as well as its use of trust scores in the COTI network.
Because COTI uses several independent clusters, each supports one token, the whole network is made infinitely more efficient and modular.
In essence, the COTI network will have several independent clusters and tokens built atop the Trustchain, with the COTI native coin used as a common means of payment for all fees and stakings inside the COTI ecosystem.
To know everything about COTI’s DAG and Consensus Algorithm, click here.
You can also watch the COTI Cluster explained — A live DAG simulation with COTI’s software engineer
To prevent the growing Cluster from becoming unmanageable in storage size, COTI has implemented the Clusterstamp, which consists of two phases:
1. The last fully confirmed transactions (having both Trustchain consensus and DSP consensus) for each account have been found. The ‘last’ transaction means that there are no fully confirmed transactions that are confirming it. These transactions then become the genesis transactions in the next generation of the Cluster.
2. All other confirmed transactions are excluded from the working DAG and kept by Full Nodes. All non-confirmed transactions are kept in the working DAG. The Clusterstamp process is performed automatically.
Clusterstamp is executed by the consensus and through verifying the last index from fully confirmed transactions. All validators (DSPs) generates balance clusterstamp themselves and check the hash. Full nodes are not taking part in this process and they are only aware of it (thus not flooding the network with retries till the process is finished). When the clusterstamp is done, all nodes do a soft restart, switching the database, writing only needed transactions to it, and re-initializing balance service. The old database is then deleted and the operation itself does not require a voting.
Following the creation and verification of a Clusterstamp, it is stored in the COTI History Nodes. History nodes are receiving copies of all propagated transactions together with confirmation states, for this reason, we do not need to copy any transaction data during the Clusterstamp. The Clusterstamp is not applicable to the smart contracts Cluster.
Finally, besides keeping the DAG operational as a data structure, the Clusterstamp has more benefits for the COTI network. The Clusterstamp provides a useful reference point and an opportunity for performing a system-wide audit to ensure that there are no inconsistencies or possible fraud.
Join us in our Telegram group for all future updates and tech developments.