what consensus mechanism does xos use?

XOS uses a customized proof‑of‑work–style consensus called xPoW (Extended Proof of Work).

What xPoW means in practice

• Blocks are produced on a regular schedule (the design discussion centers on roughly 20‑second blocks), with miners competing using an adjusted proof‑of‑work function.

• The “x” in xPoW reflects extra rules and parameters on top of classic PoW (for example, parameter evolution and fairness auditing) aimed at resisting 51% attacks, selfish mining, and time‑dilation attacks.

• Security is framed explicitly around PoW‑style threats like 51% attacks and selfish mining, and the docs describe “miners” and EIP‑1559‑like fee burning, which further confirms that XOS is PoW‑based rather than PoS or a hybrid.

Quick Scoop

If you just need the short version for a post:

XOS currently relies on an xPoW (Extended Proof‑of‑Work) consensus mechanism, i.e., a PoW‑family design with additional parameters and auditing logic intended to improve fairness and resistance to common PoW attacks.

TL;DR: XOS does not use PoS or a formal hybrid like PoW/PoS; it uses its own xPoW proof‑of‑work variant as the core consensus mechanism.

Information gathered from public forums or data available on the internet and portrayed here.