On this page
Neo is a smart-contract blockchain ecosystem with two principal native assets: NEO for governance and GAS for network use. Its current landscape includes Neo N3 and the Ethereum Virtual Machine-compatible Neo X sidechain. Those systems should not be confused with Neo Legacy, the network described in many older tutorials.
The ecosystem remains active as of October 8, 2026. Its official website lists 2026 software notices for both Neo and Neo X. Those notices document continued software work, although they do not measure commercial adoption.
Why there are two tokens
Neo's documentation separates governance from utility. NEO holders can participate in selecting the network's governing council, while GAS is used for operations such as transaction fees and smart-contract deployment. A person who holds NEO may therefore still need GAS to perform a particular action.
The token model is intended to keep governance participation conceptually distinct from paying for computation. It does not remove the market risk of either asset. NEO and GAS can have different demand drivers, supplies and prices, so a comparison should identify which token is being discussed.
The official token resource describes a fixed supply of 100 million NEO. That is a token-design figure, not a claim about how much is currently available for sale. Treasury holdings, custodial balances and circulating-supply methodologies can all affect how market data providers describe available supply.
Governance and consensus are related but different
Neo uses delegated Byzantine fault tolerance, generally abbreviated dBFT, for consensus. Consensus determines how the network agrees on valid blocks. Governance concerns who performs certain roles and how network parameters can change.
Neo's official governance material says NEO holders vote for a council that includes consensus-node responsibilities. It also describes GAS rewards for governance participation. The distribution of votes and node responsibilities matters when assessing how control works in practice.
The useful questions concern concentration and accountability: who holds voting power, which entities operate nodes, how candidates are selected and how changes are approved. A label such as decentralized cannot answer all those questions by itself. Nor does voting participation guarantee a particular financial return.
N3 changed the operational context
Neo's migration documentation distinguishes Neo Legacy from Neo N3 and describes creating an N3-compatible wallet when moving assets. The existence of separate migration instructions shows why an old address or wallet tutorial must not be assumed to apply unchanged to the newer chain.
For an older holder, identifying the network is the first step. A balance can be correctly displayed in a legacy wallet while the intended receiving service supports only N3. The asset name alone does not establish compatibility. A historical migration interface or fee schedule does not establish present eligibility for every holder.
The broader lesson is to treat chain version as part of the asset identity. It belongs alongside the token name, receiving-network support and transaction history when evaluating an old balance.
Where Neo X fits
Neo's website identifies Neo X as an EVM-based sidechain. EVM compatibility allows applications to use a development environment familiar from Ethereum, but it does not make the sidechain identical to Ethereum or to Neo N3.
A sidechain has its own operating assumptions, and moving assets between networks can add bridge-related risks. A wallet interface supporting several networks does not make transfers between them automatic. The destination chain and supported asset representation still matter.
For developers, the distinction affects tooling and deployment. For users, it affects addresses, fees, bridges and the application they are actually using. Treating the whole ecosystem as one undifferentiated blockchain hides those practical differences.
What the platform offers and what that proves
Neo presents built-in or integrated infrastructure for smart contracts, naming, oracles and distributed storage. Its developer resources support several programming languages. These are technical capabilities, not evidence that every application is secure or widely used.
An application can fail because of its own code or business model even if its host blockchain functions correctly. A bridge, custody service or exchange can create additional dependencies. Evaluating NEO therefore involves separating the chain, its governance, its applications and the token market.
Government backing and regulatory approval should not be inferred from a project's origins or technical design. For readers, the most useful starting point is clear: determine whether the subject is NEO, GAS, N3 or Neo X before comparing features or attempting a transaction.