Node Architecture
Last updated
Last updated
Circular's node architecture is designed to be simple and efficient, with each node implementing all the necessary functions to process transactions, blocks, and smart contracts. Figure 6 illustrates the internal structure of a Circular node.
At the entry point of the architecture is the Web Server (WS), which enables the node to interact with the rest of the network using a TCP/IP based protocol. All communications between nodes use signatures to ensure that each party can always be identified.
Transactions are handled by the Transaction Manager (TM), which parses incoming transactions and redirects them to the appropriate blockchain or smart contracts. Each regular transaction is added to the pending transaction list, which is available for each blockchain instance, along with the specific settings for that blockchain.
The Miner Scheduler (MS) is responsible for checking pending transactions on different blockchain instances and, when there are the right conditions, create a new block. MS requests a new ticket and prepares the block for the miner. Mining is always executed from a single Node at a time through a ticketing order, and the miner executes the mining process according to the difficulty level and other specific settings for that blockchain.
Once a block has been mined, the Circular Consensus mechanism is executed to ensure that the block is approved and added to the blockchain. The node also periodically sends requests to services or nodes to update the Nodes List and other information necessary to perform its tasks.
Finally, blocks that are approved are saved through the Disk Manager, which stores blocks and transactions in simple files or a local SQL database, depending on the type of hardware used for the node. Circular's node architecture is designed to be scalable, secure, and efficient, enabling nodes to process transactions and blocks quickly and easily while maintaining a high level of security and reliability.