cryptosnif
NEO (NEO)
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Examined promise
This dossier examines the documented purpose and mechanisms of the native NEO asset on the neo-mainnet network. The objective is to evaluate the project's stated goals against available source materials without performing live network observation or independent operational verification.
Established facts
The pinned Neo README identifies this repository as a C# implementation of Neo's blockchain protocol library. It explicitly distinguishes the library from the executable node, located in neo-project/neo-node, and from the virtual machine in neo-project/neo-vm. A protocol library supplies reusable implementation logic, while a virtual machine executes application instructions under defined rules. The overview maps separate core libraries, node plugins, private development-network tools and a .NET contract development kit. Neo Enhancement Proposals are described as covering standards, protocol specifications, client APIs and contract interfaces. No linked implementation or proposal was examined beyond this overview. The source separates native platform components from non-native contracts and points to N3 documentation. Availability of these components establishes no verified deployment, executed smart contract, adopted proposal or current governance configuration.
Unknowns
Present independent control, beneficial ownership, actual usage, client adoption, supply metrics, concentration levels, liquidity conditions, and the complete incident history remain unverified. No independently reviewed criterion observation was admitted in this documentary lot for identity, usage, token-role, supply, concentration, value-capture, control, security, governance, accountability, incidents, continuity, or execution.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The absence of live network observation means that the gap between the documented protocol library and the functioning mainnet remains unbridged by this review. Operational strength remains unproven. The project holds an unrated status with 0% scoring coverage across all dimensions including technology, usage, economics, governance, resilience, and liquidity.
Verdict
Operational strength remains unproven; unrated with 0% scoring coverage. The dossier confirms the existence of pinned documentation but does not verify active network participation, asset distribution, or governance structures. Missing essential criteria such as identity, supply, and control prevent any rating assignment. This documentation review is not an independent operational verification.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this assessment. These must be followed by calibration and editorial review to move from an unrated status to a scored evaluation. Without such data, the conclusion that operational strength is unproven stands.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Validator independence, upgrades, execution and fees.
Inspect the evidence
Sources behind this analysis
NEO: pinned neo-project/neo overview (06e9058c1606)
The pinned Neo README identifies this repository as a C# implementation of Neo's blockchain protocol library. It explicitly distinguishes the library from the executable node, located in neo-project/neo-node, and from the virtual machine in neo-project/neo-vm. A protocol library supplies reusable implementation logic, while a virtual machine executes application instructions under defined rules. The overview maps separate core libraries, node plugins, private development-network tools and a .NET contract development kit. Neo Enhancement Proposals are described as covering standards, protocol specifications, client APIs and contract interfaces. No linked implementation or proposal was examined beyond this overview. The source separates native platform components from non-native contracts and points to N3 documentation. Availability of these components establishes no verified deployment, executed smart contract, adopted proposal or current governance configuration. No software, node, transaction, governance vote or benchmark was executed in this review. Current deployed versions, participant independence, economic rules, usage, supply, ownership, concentration, liquidity and the complete incident record remain independently unverified. Descriptions of architecture establish a research scope and supply no investment-return forecast or operational safety guarantee.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.