# The Xvitesse Blockchain ## Network Overview and Key Metrics Xvitesse is the decentralized EVM-compatible public blockchain that powers the Xvitesse platform and ecosystem. It is fully compatible with Ethereum meaning that any smart contract that can be deployed on the latter can also run on top of Xvitesse. The Xvitesse blockchain uses a variant of delegated Proof of Stake (dPoS) for achieving [consensus](https://docs.xvitesse.com/general/fuse-network-blockchain/fuse-consensus). The consensus is secured by a significant number of independent validators, only one of which is run by the Xvitesse core team. Validators are also responsible for the most important type of governance on Xvitesse, namely, adopting the network protocol changes via Xvitesse Improvement Proposals. The native token of the network is called XVI. New XVI tokens are issued with every added block and are also used to pay for gas, just like ETH on Ethereum. The Xvitesse blockchain is designed to ensure fast block confirmation times and a low cost of transactions. The average block interval on Xvitesse is around 12 seconds, and it currently at a negligible fee to get a transaction confirmed. In its present capacity, the Xvitesse blockchain is capable of processing around 120 native token transfers and 60 XSC20 token transfers per second. The faster processing of native token transfers is because they do not involve computations run on the network's virtual machine. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.xvitesse.com/general/learn-about-the-xvitesse-platform/xvi-network-blockchain.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.