- NEO Overview
- Asset Role and Supply
- Market Structure
- YearBull Perspective
- Key Risks
- Primary Sources and Review Scope
- NEO: A Dual-Token Smart-Contract Network Built Around On-Chain Elections
- What NEO is designed to do
- How N3 processes transactions
- NeoVM and the application layer
- What the NEO token does
- Governance is a core dependency
- Limitations and open questions
- Key takeaways
- Risks and open questions
- YearBull Rank on this page
NEO Overview
NEO (NEO) is tracked under neo. The local profile associates it with Smart Contract Platform, Proof of Stake (PoS), Made in China. A recorded genesis or launch date is 2016-10-17. The source profile treats it as native or does not identify a separate token platform.
Asset Role and Supply
Its role should be evaluated through network or product use, supply design, governance, liquidity, and trading-venue quality. The reviewed record shows circulating supply about 70.53 million NEO, total supply about 100.00 million NEO. It records no hard maximum. Supply fields may change through issuance, burns, migrations, or source revisions and should be checked against project records.
Market Structure
At the 2026-09-12 review, the local snapshot placed NEO at market-cap rank #208, with market capitalization about $155.36 million and reported 24-hour volume of $3.98 million. These values describe observed scale and turnover, not fair value or guaranteed executable liquidity.
YearBull Perspective
The dated snapshot recorded YearBull Rank #431, Bull Score 68/100, Risk Low, and Cycle Early. Rank, Bull, Risk, and Cycle answer different questions and should be read together.
Key Risks
Material risks include market volatility, liquidity deterioration, protocol or governance failure, concentration, and regulatory change. Historical prices, rankings, and classifications do not predict future performance. Verify contract addresses, network support, custody, and venue availability before acting.
Primary Sources and Review Scope
YearBull methodology · Official website · Technical documentation or whitepaper · Source repository. Profile and market fields were checked against locally stored source records on 2026-09-12. The live snapshot above may be newer than this editorial review.
NEO: A Dual-Token Smart-Contract Network Built Around On-Chain Elections
NEO is a smart-contract platform whose design separates network governance from transaction payment. Its N3 architecture combines elected consensus, a native virtual machine, protocol-level services, and a token model in which NEO grants voting rights while GAS pays for computation and storage.
What NEO is designed to do
NEO is a public blockchain for deploying smart contracts and decentralized applications. The current N3 architecture is presented as a full-stack platform rather than only a settlement layer: its native components include smart contracts, an oracle service, decentralized storage through NeoFS, a naming service, identity tools, and interoperability features. These services are intended to reduce the need for applications to assemble every dependency externally, although developers still depend on the availability and correct operation of those components.
The project’s implementation is split across several open-source repositories. The core neo repository contains the C# protocol implementation, while the node software and NeoVM are maintained separately. This separation matters for users and developers because running a node, executing contracts, and building applications involve different software components rather than one single client package.
How N3 processes transactions
NEO uses delegated Byzantine Fault Tolerance, or dBFT, rather than proof-of-work mining. NEO holders vote for candidates, and the elected consensus nodes propose and commit blocks. The project’s documentation describes a committee of 21 members and seven consensus nodes under the default configuration; the consensus group is responsible for block production, while the wider committee can adjust selected network parameters. Elections are recalculated every 21 blocks, allowing the validator set to change as voting balances change.
The principal benefit claimed for dBFT is single-block finality. A block is committed after the required validator signatures are collected, and the protocol includes view changes and a recovery mechanism if the current speaker or communication path fails. This can make confirmation behavior easier for applications to reason about than systems where blocks may later be reorganized. It does not remove the need to assess validator concentration, software defects, network availability, or governance capture.
NeoVM and the application layer
NeoVM is the execution environment for NEO smart contracts. The project describes it as a Turing-complete virtual machine whose contracts are compiled into a common NeoVM instruction format. Official developer materials support languages including C# and Java, allowing developers to work with familiar ecosystems before producing NeoVM-compatible bytecode. The core repository identifies NeoVM, node software, developer tooling, and contract libraries as separate parts of the broader stack.
N3 also exposes native contracts for functions that applications may need repeatedly. The documented native set includes NEO, GAS, contract management, the ledger, policy controls, role management, cryptography, and the oracle service. NeoFS adds a storage layer whose permissions are tied to wallet addresses, while the oracle service can request data from HTTPS or NeoFS sources. These features expand what applications can attempt, but they also create practical dependencies on service operators, data providers, node software, and contract correctness.
What the NEO token does
NEO is the governance token of N3 and has a maximum supply of 100 million whole units; it is not divisible. Holders can vote for candidates, helping determine the committee and consensus nodes. The protocol also links NEO ownership to GAS generation. The documented incentive design allocates newly generated GAS among NEO holders, committee and consensus participants, and voters, with the largest stated share directed to holders who vote for elected members.
GAS is separate from NEO and is used to pay for transactions and other network resources, including contract execution and storage-related operations. In N3, system fees are burned according to the project documentation, while GAS generation has no stated maximum supply. This creates a clear division of roles: NEO provides governance weight, while GAS is the operational payment asset. Holding NEO therefore does not by itself substitute for having GAS available when an account must pay network fees.
Governance is a core dependency
NEO’s governance is not limited to signaling. The committee can influence network parameters such as fee settings, execution costs, storage pricing, and account policies, while consensus nodes control block production. Voting weight is based on the NEO associated with voting addresses, so participation and concentration of NEO can affect who controls these operational decisions. The model offers a formal route for changing network behavior, but it also makes voter distribution and candidate independence material questions for users.
The transition from Neo Legacy to N3 is another operational consideration. Official migration documentation describes a separate process for moving NEO and GAS from the legacy chain to N3, with specific address, transaction, fee, and asset rules. Users interacting with wallets, exchanges, or applications must therefore confirm which network an asset belongs to rather than treating every NEO balance or contract address as interchangeable.
Limitations and open questions
The main architectural trade-off is between fast, deterministic consensus and a relatively small elected validator set. NEO’s official materials describe fault tolerance assumptions for dBFT, but an academic analysis of an earlier implementation identified possible safety attacks and reported that fixes were accepted by the official team. That history does not establish a current vulnerability in N3, but it shows why claims about finality should be evaluated against the exact software version, validator configuration, and subsequent code changes.
A second question is ecosystem depth. N3 offers several built-in services, but the usefulness of those services depends on developers deploying applications, users generating activity, and infrastructure providers maintaining compatible tooling. The project’s documentation confirms the available mechanisms; it does not, by itself, demonstrate sustained adoption, economic demand, or independence from the organizations most closely involved with the network.
Key takeaways
- NEO is the governance asset; GAS is the network payment asset.
- N3 uses elected validators and dBFT rather than proof-of-work mining.
- NeoVM supports smart contracts, while native contracts provide protocol-level services.
- NeoFS, the oracle service, naming, and identity tools are useful dependencies as well as potential failure points.
- Legacy-to-N3 migration means users must verify the network and asset format before transacting.
- The small elected validator set makes governance distribution and implementation quality central to the risk assessment.
Risks and open questions
- Validator and voting concentration may reduce practical governance diversity even though candidate registration and voting are open.
- The security properties of dBFT depend on the exact deployed implementation, validator set, communication assumptions, and subsequent fixes.
- NeoFS, oracle requests, identity tooling, and interoperability introduce dependencies beyond the base ledger.
- GAS has no stated maximum supply in N3, so future issuance and fee policy can affect the economic role of the two-token model.
- Legacy and N3 assets, wallets, and application contracts are not automatically interchangeable.
- Official feature documentation establishes intended functionality, but does not independently demonstrate broad application adoption or sustained user demand.
YearBull Rank on this page
YearBull Rank now for neo: #541.
Rank change (daily snapshots).
Reading rule: lower is better in this ranking.
- 7d window (2026-09-13): #186 → #541 (down by 355).
- 30d window (2026-08-21): #1259 → #541 (up by 718).
Liquidity note: If the line improves during quiet periods, it can be accumulation. relative rank is sensitive to who is active in the window.
Listing context: If the line is step-like, watch for discrete market changes. a new route can show up as a step change.
Regime context: If both windows align, the direction is clearer. a stable phase often tightens the rank range.
Risk posture: If the curve is step-like, it may be reacting to discrete inputs. ranking moves can reflect regime shifts rather than one-off events.
Practical note: read the move, then read the stability of the move.
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. Smaller numbers mean the coin sits higher in the YearBull list.
