STATIC (Services Transactions and Trusted-in-Control) nodes form the backbone of the XTRABYTES™ network. They perform a crucial role in the consensus, security, and governance of the platform. It’s the STATIC nodes that are tasked with verifying transaction blocks, much the same as full nodes do for the Bitcoin network. They store the entire blockchain and ensure new blocks follow the consensus rules. However, the rules to do so are somewhat different.
For instance, XTRABYTES uses a new consensus algorithm called Proof-of-Signature rather than the more common Proof of Work consensus. Instead of transactions being passed on to miners, transactions blocks are validated by the nodes that are online at the time these transactions occur. Nodes that are offline double check these blocks when they come online again, though they are not required to sign the transactions themselves. Thus, even one online STATIC node could theoretically run the whole network. In order for this to work, STATIC nodes not only need to be known and trusted but communicate easily and effectively.
Consequently, the XTRABYTES network has been designed with great care. When confirming transactions, the XTRABYTES network uses an upper layer of the network we can call the Virtual Chord Network. Each STATIC node is connected to one “virtual chord node”, which are only virtual nodes rather than “real” (hardware) nodes. This is why it is not important how many STATIC nodes exist or how many STATIC nodes are online or offline at any given time, as the number of overview virtual network nodes remains constant.
In the case of XTRABYTES, this virtual chord network is known as VITALS (Virtual Information Transmissions Aligning STATICS). VITALS serves as the pathway between nodes, a proprietary network that provides VPN-like functionality to the STATIC nodes. More specifically, VITALS interconnects online STATIC nodes using a private virtual network, thus ensuring interference-free direct paths between these nodes. Not incidentally, the VITALS network contains fixed virtual (chord) nodes that correspond to one or more of the STATIC nodes. Additionally, STATIC nodes use the PULSE (Ping Unified Ledger Synchronization Equalizer) network to communicate with each other directly. Its PULSE that actually alerts the STATIC nodes when a transaction block must be validated.
Block communication is controlled entirely through the communication (using PULSE) between the VITALS and the system of physical STATIC nodes. When a transaction is created, it is signalled to and verified by all the STATIC nodes in the network. Once the transaction has been completely validated (every STATIC has signed the transaction), the VITALS network proceeds to create the new block and achieve 100% signature validation of that new block. Using this method of block creation, XTRABYTES avoids transaction and block conflicts while allowing every peer knowledge of who will create the new block and who will distribute the block first.
How can I register a STATIC Node?
It's important to realize that STATIC node is a deposit, not a cost. Thus, the actual deposit is yours and you will get it back if you ever decide to break your node.
There will be no fee for registering the nodes.
Are there any plans to restructure the prices for statics as XBY increases in value?
The XTRABYTES team will modify STATIC numbers if community members decide STATIC prices are too high. At present, we do not intend to pursue such an action since many investors are patiently waiting to send in their STATIC deposits. As it stands, the XTRABYTES community currently perceives Level 1 nodes as amenable to corporate-level ownership (where a large corporation may seek to buy the STATIC from its initial owner).
Eventually, the community will have to decide if it is time for a “halving”. When halving occurs, STATICs double in number while coin numbers remain constant. If that were to occur, XTRABYTES would host 1024 Level 1 STATICs that held 250,000 XBY coins each. The same would occur for the other two STATIC levels. Thus, performing a halving would cut the the deposit requirement for each STATIC node in half. Node owners then have the option to either sell one or both STATICS, break one or both STATICS, keep both STATICS on the same server or for optimal results, keep both STATICS but set up a new server for the new STATIC.
Halving may occur any time deemed necessary, particularly if the market greatly expands. Coupling is also a future possibility if the market heavily retracts (since fewer STATICS would be needed to run the network).