Neo has the stack, the treasury,
and a definable 2030 opportunity.
Independent research on Neo's 2026–2030 product opportunity — assembled from public primary sources, source-linked throughout, and published as a peer artifact to the Meteor initiative. The through-line: Neo has quietly shipped the only major-L1 stack combining a protocol-native oracle, decentralised storage (NeoFS) priced in the host-chain asset, hard finality (dBFT 2.0), and a consumption dual-token model. There is a real market opportunity worth preserving. The governance work required to capture it — asset consolidation, disclosure discipline, accountable execution — is definable and, in principle, achievable.
By 2030, Neo becomes the verifiable data-supply layer for autonomous decision systems — capturing $6.5M–$255M/year in GAS burn from prediction markets, DePIN, content provenance, and RWA infrastructure. Supplier position first; runtime position earned organically over time.
Neo has, in production, an unusual combination of blockchain primitives — protocol-native oracle, decentralised storage (NeoFS) priced in the host-chain asset, deterministic finality (dBFT 2.0), and a dual-token consumption model. Independently of the governance situation, the 2026–2030 blockchain market is producing several segments (content provenance, DePIN storage-integration, prediction markets, agent compliance, enterprise ML lineage) whose primitive requirements map cleanly onto that stack. Meanwhile, the Neo Foundation + NGD custody $460.8M in assets and the co-founders have published incompatible near-term product directions and are no longer coordinating on mainnet direction.
This publication asks two related questions: (1) which 2026–2030 market segments does Neo's architectural distinctiveness actually address, and how large is the associated GAS-burn opportunity by 2030? (2) which governance structures are load-bearing preconditions for capturing that opportunity, given the current founder split and treasury custody state? The research is published as a peer artifact to Neo's Meteor product-strategy initiative — independent inputs producing potentially convergent (or divergent) outputs.
- Independent market ranking of 12 segments (Tab 3) produces a top-5 shortlist where four of five converge on the same underlying primitive: verifiable data supply (Oracle + NeoFS + dBFT + dual-token GAS pricing). Interpretation
- NF + NGD custody $460.8M as of Dec 2025; 86% of NF assets are in single-signature custody with no dated multi-sig migration milestone (Tab 6). Fact The interpretation that this is a materially larger structural governance issue than any single downstream spending decision is analytical framing. Interpretation
- Governance stall is not a strategy problem — it is an execution and accountability problem (Tab 5). Fee reductions, block-time optimizations, and reward reforms were agreed and then stalled for months due to unclear ownership. Sourced claim
- Meteor's methodology is sound; four structural role dynamics in the Phase 0 seat composition — voter/executor overlap, participant-journalism, founder technical proxy, unnamed research firm + seat stacking — would predictably narrow the output regardless of process quality (Tab 4). Interpretation
- Committee participation: on a specific proposed multisig transaction, only 2 of 21 committee members signalled willingness to sign — below the 11-of-21 threshold, so not broadcast on-chain. Author observation from Neo governance channels; specific proposal ID pending v1.0.1. Sourced claim Whether this low-water figure is a one-off or a recurring pattern across N3 lifetime is not consolidated here. Unknown / gap
- Neo's defensible position is as a verifiable-data-supply layer priced entirely in GAS, addressing sub-markets where architectural fit outweighs incumbent distribution moat. The customer segments differ; the primitive is one.
- The wedge question is sequencing, not selection: which of the five convergent segments produces the first case study and unit economics fastest. DePIN and provenance anchoring are the two natural candidates.
- Neither founder camp's product frame captures the primitive on its own. The data-supply thesis is compatible with both — but only if governance can produce accountable execution across founder lines.
- The unmandated-authority pattern is chain-wide, not faction-specific. Historical NF/NGD treasury deployment and the 2026 temporary committee are two instances of the same operating model, at different scales.
- Custody consolidation + independent staff to execute Foundation commitments is the load-bearing precondition. Without it, any product direction — Meteor's or independent — sits on the same unstable base.
- Consolidate custody first. Multi-sig migration with a public milestone plan; independent audit deliverable, not promise.
- Broaden the Meteor research seat composition before Phase 0 output publishes — add one independent-of-founders analyst; identify the unnamed research firm; resolve the participant-journalism disclosure.
- Publish the full historical treasury deployment for 2020–2025 at the same granularity as the 2025 report, including recipient lists for community-project grants and outcomes.
- Adopt a named-accountability sequencing: asset consolidation (#4532) → governance restoration (#4531) / restructuring (#4526) → named execution owners → product direction. Product direction downstream of execution accountability, not upstream.
- Compare rankings. When Meteor Phase 0 publishes, compare the ranked shortlist against the independent ranking in Tab 3. Convergence is load-bearing; divergence is diagnostic.
Full detail per audience (holder / contributor / journalist / Council member) in Tab 8 · Way Forward.
Pick your entry — surface for holders, expandable modules for analysts, dedicated tabs for insiders.
Recommended path: Overview → North Star (02) → Diagnosis (05) → Treasury (06) → Way Forward (08). Skip Market Research (03) unless you want the depth.
Recommended path: Overview (01) → Market Research (03) → Meteor (04) → Diagnosis (05) → Treasury (06) → Governance (07) → Sources (10). Every claim traces to a public source.
Recommended path: North Star (02) → Market Research (03) → Meteor (04) → Governance (07) → Treasury (06). You already know the timeline — start with the decision matrices.
- Independent — no NF grant, no NGD funding. Disclosure: as of 2026-08-25, the author holds one Meteor Phase 0 research-team seat, ceded by Council member deanragnarok in his stead. See Tab 4.
- Source-linked — every claim carries a public citation
- Confidence-tagged — projections labeled high / medium / speculative
- Falsifiable — 6 named criteria that, if unmet, prove the thesis wrong
- Living — placeholders visible for charts + research still in flight
- Not funded by any Neo entity, exchange, or investor
- Not aligned with either founder — analysis applies to both
- Not a governance proposal — see #4526, #4531, #4532 for those
- Not final — the report will update as the ecosystem responds
Neo doesn't have a strategy problem.
It has an execution and accountability problem. Meteor is a strategy process. The strategy question is downstream of a governance layer that cannot enforce what it decides. Fix the accountability first — or the ranked shortlist of "product directions" is just a ranked shortlist of directions that also won't ship.
Neo doesn't have a strategy problem. It has an execution and accountability problem. Meteor is a strategy process.
— Malcolm Lerider, Meteor statement · 2026-08-18Neo has been drifting because no one picked a product direction. If a rigorous process ranks the candidates and produces a shortlist, execution will follow.
Fee reductions, block-time changes, and reward reforms have been agreed and then stalled for months due to unclear ownership. Two founders publicly disagree. On at least one proposed multisig transaction, only 2 of 21 committee members signalled willingness to sign — well below the 11-of-21 threshold.
A ranked shortlist adds a new item to the queue. The queue is the problem. Until someone is named and accountable for shipping, the next shortlist will follow the last one into the drawer.
Both founder camps treat NEO/GAS spending as operational funding without business cases. Malcolm's ROI critique: "1 spent NEO/GAS should give >1 back." Neither camp is managing it that way. The temp committee spent ~$1.2M in six weeks with no return metric attached. NGD's grant program uses similar mechanics. The problem isn't which product to fund — it's that funding doesn't require a return.
Reframes the treasury question from transparency (Erik's frame) and consolidation (Malcolm's earlier frame) to basic financial competence. TIMELINE · 2026-07-09
NF + NGD hold 41.17M NEO (41.2% of supply) against ~14M NEO actually voting for consensus. Foundation weight ≈ 3× the entire non-Foundation electorate. 86% of NF assets sit in single-signature custody, meaning individual keyholders — not NF-the-institution — cast the vote. The Council is not elected; it is appointed by NF.
Implication: every council-driven process, including Meteor, is functionally an NF-appointed process regardless of procedural legitimacy. Only Da's #4526 targets the meta-lock directly (redistribute ~26M NEO, cap NF reserve at 5–10M). Erik's #4531 does not. Dean's 2+2+1 does not. Malcolm's #4532 as originally scoped does not. NF FINANCIAL REPORT DA #4526 COINDESK 2026-04-16
Meteor treats "which product direction wins" as the missing decision. But the ecosystem has agreed on many things that never shipped. The bottleneck isn't choice — it's the layer beneath it.
Three prior agreements that stalled:
- Council fee reduction — agreed at Centre Point 2 (Oct 2025), partially executed (1000 → 750 GAS), full 100× reduction still stalled
- Block time optimization — extensively discussed in #council-and-core, no shipping date
- Reward mechanism reform — Erik's tiered rewards proposal (#4467), aligned with STB proposal (#4411), no consensus vote reached
None of these are strategy questions. All were failed by the same execution/accountability structure that Meteor would hand its Phase 0 output to.
The two Neo Foundation co-founders have published incompatible near-term directions and are, per public reporting, no longer coordinating on mainnet direction. Meteor sits inside this split, not above it. Understanding the split as a governance problem — not a personality problem — matters because it shapes what any Phase 0 process can and cannot produce.
Neo X positioned as AI-agent-native chain. Autonomous agents as primary on-chain users. Parallel ventures include an agentic OS (SpoonOS, $2M dev fund, launched Apr 2026) and a separate blockchain with its own token (AEON). Per Yahoo Finance summary, the AEON funding structure is one specific concern that contributed to the founder split.
OneGate positioned as decentralized identity for everyday users. The NEP-20/21/33 authentication stack shipped in April 2026. An August 14 article restated OneGate as forward-looking "vision" two days before Meteor launch — no post-launch adoption metrics (DAU/MAU, application count, retention) were disclosed alongside.
This publication's frame: Neo as verifiable data-supply layer that autonomous decision systems consume from — priced in GAS, settling on Neo regardless of which chain the consuming agent runs on. Supplier position first; runtime position earned organically. Independent of either founder frame.
TAB 2 · NORTH STARA third-party mediator has been working with both founders since spring 2026. The proposed board structure — 2 Da picks + 2 Erik picks + 1 independent — would make the independent seat the swing vote by design. Per public statements as of mid-July 2026, the first structured meeting with Erik had been confirmed. The substance of specific conversations, precise timing, and contingency plans have not been publicly disclosed.
Three competing proposals. Four days.
Zero on-chain consensus.
Between April 9 and April 13, 2026, the two founders and one independent NEO holder each published governance proposals with fundamentally different first steps. None has passed. On at least one proposed committee-multisig transaction, only 2 of 21 members signalled willingness to sign — below the 11-of-21 threshold, so the proposal was not broadcast on-chain. The proposals below and the deadlock mechanics that hold them are the substance of the governance crisis.
| Dimension | #4526 — Da Hongfei | #4531 — Erik Zhang | #4532 — Malcolm Lerider |
|---|---|---|---|
| Approach | Institutional redesign | Constitutional restoration | Precondition, not governance |
| First step | Redomicile to Cayman Islands | Establish on-chain supremacy in constitution | Transfer all Neo assets to NF |
| Timeline | 12 months (4 phases) | 4 phases (unspecified duration) | Immediate (3 sentences) |
| Board structure | 5 seats · community/veterans/independent · 2-year staggered terms | 5 seats · domain-specific (Protocol, Engineering, Treasury/Audit, Treasury Strategy, BD) | Not specified — deferred to post-consolidation |
| Founder role | Excluded from Board 24 months, then eligible as ordinary members | Permanent conflict-of-interest exclusion for competing-project participants | Not addressed |
| Voting model | Staked voting · 180-day unbonding · NEO made divisible | Any NEO holder at snapshot · liquid voting preserved | Not specified |
| Asset scope | NF + NGD assets consolidated under redomiciled Foundation | Maximalist — all substantively Neo-related assets (control/beneficial/funding basis) | All Neo-related assets → existing NF |
| Redistribution | Giveback II — ~26M NEO + 40M GAS to holders via protocol rebasing | Frozen pending investigation; no redistribution described | Out of scope |
| Accountability | Tokenholder emergency powers + Cayman Grand Court backstop | Permanent liquidation + accountability duties · "shall not be suspended" | Implicit — enables all downstream accountability |
| Meta-lock addressed? | YES Redistribute; cap NF reserve 5–10M | NO Changes signers, not holders | NO Original scope; §9.7 re-review |
| Source | #4526 | #4531 | #4532 |
#4526 — Five measures + Giveback II allocation
Measure 1 · Redomicile — Move NF from Singapore CLG to memberless Cayman Islands foundation company with bespoke bylaws + independent professional supervisory agency. 3 months.
Measure 2 · Governance Framework — 5-seat Board · Supervisor (independent agency) · founder exclusion 24 months · three governance layers (internal, bylaws/tokenholder powers, Cayman Grand Court backstop).
Measure 3 · Staked Voting — Replace liquid voting with time-locked staked voting · 180-day unbonding · NEO made divisible. 6–9 months, coordinated with Giveback II.
Measure 4 · Giveback II — NF+NGD hold 41M NEO + 40M GAS · 33M NEO + 35M GAS in single-sig.
| Allocation | Amount | Terms |
|---|---|---|
| NF strategic reserve | ~5–10M NEO | Staked indefinitely · GAS = perpetual NF revenue |
| Community groups | ~5–10M NEO | Mandatory staking 4y · GAS = operating funds · predefined unstaking |
| Tokenholder rebasing | ~26M NEO + 40M GAS | Protocol-level proportional distribution at specified block height · requires exchange custodial support |
Measure 5 · Asset Consolidation & Financial Discipline — Transferable assets → Foundation outright · non-financial assets (domains, social, trademarks, IP, repos) → Foundation custody · unified funding model · no NEO liquidation for operations · annual financial report.
#4531 — Seven governance principles + maximalist Neo Public Assets
Seven principles: On-chain verifiability · Community authorization · Corresponding authority & responsibility · Duty of loyalty & conflict-of-interest exclusion · Continuous transparency · Legal incorporation · Substantive attribution.
Neo Public Asset definition — Substance-based, not title-based. Covers all NF/NGD assets, founder nominee holdings, all on-chain assets, all off-chain assets, all investment interests, and "other assets not formally in NF/NGD name but whose substantive benefit belongs to Neo's public governance."
5-seat Board (domain-specific): Protocol & Architecture · Engineering & Infrastructure · Treasury Audit & Compliance · Treasury Strategy & Investment · Business Development & Strategic Partnerships.
Permanent duties — Transparency, liquidation, accountability duties "shall not be suspended, extinguished, or circumvented by governance restructuring, legal-entity restructuring, or changes in responsibilities."
Voting eligibility: Any NEO holder at snapshot time. No identity/region/off-chain restrictions. Nomination requires minimum NEO threshold; nomination eligibility does not affect equal right of all holders to vote.
#4532 — The three-sentence precondition
Core argument: All assets serving Neo's public interest — whether controlled by NGD, founders, or any affiliated entity — should be moved to the existing Neo Foundation. This is not a governance proposal but a precondition for any governance proposal. The Foundation's structure (board composition, oversight, decision-making) is a separate topic — but that discussion is meaningless while assets remain fragmented across entities with unclear control.
Sequence: Transfer first. Then decide how to govern.
Closing line: "I am sorry this needed to be a proposal."
Author's honest re-review (from whitepaper §9.7): as originally scoped, #4532 changes who signs for NEO, not who holds NEO. It doesn't clear the meta-lock unless paired with a redistribution or dilution mechanic.
Tyler / lllwvlvwlll — 7 accountability proposals (#224–#230)
Published 2026-04-14. Seven proposals covering: legal structure, voting, board composition, founder boundaries, asset stewardship, accountability, tokenomics. Systemic framework complementing the three founder-triangulation proposals. Broad scope; distributed adoption path.
Neo's on-chain governance body is the Council: 21 seats. The top 7 by voting weight are also the consensus nodes that produce blocks; the remaining 14 seats have no operational duty but still collect GAS from the 10% committee-reward pool. All 21 seats are elected via NEO holder voting, but because NF + NGD collectively hold ~41% of supply, the elected set is effectively appointed.
The observation is narrower than "the Council voted 2 of 21": on a specific proposed committee-multisig transaction, only 2 of the 21 committee members signalled willingness to sign. Protocol parameter changes require 11-of-21 committee signatures; below that threshold, a proposed transaction is typically not broadcast on-chain at all, so the primary evidence lives in Discord and GitHub rather than in the on-chain record. The specific proposal ID and message capture will be added in v1.0.1. Whether the low-water figure is a one-off or a recurring pattern across N3 lifetime is an open research question.
Map the 21 Council seats. Publish current occupants, tenure, voting participation, and documented ecosystem contributions on a per-seat basis. Reconstruct the historical picture where possible rather than only current snapshot. Deferred to a later iteration; the deferral is intentional.
Council voter turnout data across N3 lifetime. Populate proposal-by-proposal seat participation for all N3 governance votes to date. Would show whether the 2-of-21 pattern is recent or structural.
Other community proposals beyond the featured three. Tyler's #224–#230 accountability set is referenced; a broader inventory of community proposals (Roman Khimov, ixje, shargon, and others in Council & Core Discord) is worth compiling so the proposal picture is not implicitly reduced to the three founder-triangulation proposals.
Comparison L1 governance benchmarks. Ethereum Foundation (0.16% of supply), Solana Foundation Delegation Program, Cosmos ICF endorsement policy — how did comparable chains redistribute treasury and preserve legitimacy? Precedents referenced but not yet fully documented here.
Under whose authority?
With what transparency?
How have Neo's public assets been controlled and deployed over time, under whose authority, with what transparency, and with what accountability to the community?
— Core treasury question this section works againstNeo Foundation + NGD together custody $460.8M in assets as of the December 2025 financial report — the first comprehensive disclosure since H1 2020. This section examines that treasury against the core question above. The temporary committee's $1.2M spend across April–May 2026 is the most recent and most visible governance flashpoint, but the historical NGD / NF asset deployment is materially larger, has run over more years, and warrants comparable scrutiny. Where the public record is incomplete, this section flags the information gap rather than assuming wrongdoing.
Treasury oversight requires distinguishing between fundamentally different asset states. This report separates:
Custodied, unspent. Question: who controls the keys?
Earmarked for specific programs but not yet disbursed. Question: allocated by what authority?
Actually disbursed. Question: with what mandate and what disclosure?
Deployed into third-party equity, funds, or protocols. Question: on whose balance sheet, with what returns?
| NEO (single-sig) | 33.09M | $115.97M |
| NEO (multi-sig 3-of-4) | 6.70M | $23.48M |
| GAS (single-sig) | 35.34M | $71.70M |
| GAS (multi-sig) | 2.93M | $5.94M |
| BTC (receivable*) | 80 | $7.00M |
| Other (single-sig) | — | $0.61M |
* 80 BTC receivable is due from Erik Zhang personally per the financial report. 86% of NF assets are in single-signature custody per the report.
| Cash & equivalents | — | ~$118.6M |
| BTC | ~1,112 | ~$93.6M |
| Portfolio (investments at book) | — | $11.3M |
| Multi-sig (NEO only) | — | $0.876M |
| Other tokens | — | ~$1M |
NGD holds majority of assets in exchanges and banks per the financial report. NGD is the "principal operational arm"; NF has no independent staff (excluding founders) and no bank or exchange accounts of its own.
$187.7M in NF assets sits under a single-signature wallet controlled by one keyholder (Erik Zhang, per the report and CoinDesk's April 2026 coverage). The multi-signature transition is committed to in the financial report but has no dated milestone. This is a materially larger governance issue than any single spending decision downstream of it — a single-key compromise or single-key change of intent moves ~40% of NEO supply.
2025 total expenditure per the financial report. Prior-year breakdowns are not publicly available at comparable granularity — the 2025 report is the first comprehensive disclosure since H1 2020. Historical deployment across the 2020–2024 gap is a material information gap flagged for further research.
| Category | Share | Sub-breakdown | Est. USD | Mandate / authority |
|---|---|---|---|---|
| Core operations | 55.5% | Salaries 36.6% · operational 8.8% · marketing & events 7.7% · maintenance 2.4% | ~$10.0M | NGD executive discretion; no published headcount |
| Community & ecosystem | 39.0% | Developer grants 28.4% · Neo Bond rewards 7% · partnerships 3.6% | ~$7.0M | Grant program mechanics not fully public |
| Investments | 5.5% | Fund-of-funds and direct investments | ~$1.0M | Portfolio held at $11.3M book (Appendix B) |
The financial report states there were no exceptional items, executive distributions, or unplanned capital deployments in 2025. This is a factual claim in the report and has not been independently audited — the report itself promises an independent audit as a future deliverable, not a delivered one.
Historical spending category deep-dive. The financial report presents 2025 aggregates. A more granular examination of NGD's historical deployment — Council-node subsidies, consensus-node operating support, community-project grants (recipient list, deliverables, outcomes), ecosystem funding recipients, development program disbursements, investment holdings and returns, and operating expenditure over 2020–2025 — is required before drawing conclusions about historical spending discipline. Where data is unavailable, flag the gap rather than assume wrongdoing.
The financial report confirms — for the first time on the record — that a Neo-adjacent early Binance investment exists (per Binance's founder). Per the report itself:
- Investment made around Binance's launch (approximately 2017)
- Zero financial or non-financial returns received to date (no dividends, no BNB, no listing terms, no business opportunities)
- Carried at cost; no reliable fair value information; no market comparable
- Previous negotiations failed to reach a valuation agreement
- Currently managed by NGD (report's wording); NGD "intends to pursue liquidation and redeploy proceeds"
Open question flagged, not asserted: the report says "managed by NGD," not "owned by Neo." If the investment was made personally before NF/NGD existed as legal entities, ownership is structurally ambiguous and the destination of any liquidation proceeds is not clear from the public record. This is the kind of clarification that only NF/NGD or an independent audit can resolve.
NF 2025 FINANCIAL REPORTNF holds $224.7M in assets and has committed — in the same document — to multi-sig transition, annual reporting, an independent audit, community governance structures, and a full restructuring by end of 2026, with no independent staff (excluding founders) to execute any of it. Only two founders who are no longer coordinating and who both hold other full-time responsibilities. Every promise in the report requires someone to draft the charter, coordinate the multi-sig migration, run community consultation, and interface between the two founders. That role does not currently exist. The gap is not a criticism of the report — the report surfaces it explicitly. It is a criticism of the operating model that produced the report.
In the context of the historical treasury picture above, the temporary committee's April–May 2026 spending is one specific, recent, and highly visible instance of the broader pattern of Neo-Foundation-adjacent authority deploying assets without an explicit community mandate. It is not the largest such deployment historically, and it should not be treated as the report's dominant governance concern by default. It is, however, the most fully documented recent instance — the temp-committee transparency portal is what made the granular disclosure possible.
Disclosed via transparency portal, 2026-05-28. Total: ~424,000 NEO (~$1.2M). Committee was never voted in by the community.
| Date | Amount (NEO) | Est. USD | Label (as disclosed) | Detail |
|---|---|---|---|---|
| Apr 18 | 280,000 | ~$792,000 | "Salaries covering October 2025 to April 2026" | 7-month back-pay · ~40k NEO/month (~$113k/month) · headcount not disclosed |
| May 11 | 38,500 | ~$109,000 | "Staff salaries for May 2026" | Confirms ~$110k/month recurring run-rate · no roles disclosed |
| May 18 | 106,540 | ~$301,000 | "Confidential infrastructure-related expenditure" | The $300k question. Erik: "details cannot be disclosed at this stage." |
For context on what community-facing disbursement disclosure looks like in the same ecosystem in the same period: COZ's Proof of Working 2.5 program distributed 537 NEO (~$1,500) in April/May 2026 to 5 named projects with open-source deliverables and bi-weekly cadence. This is a comparator, not a like-for-like functional equivalent (COZ is not doing the temp-committee's operational function). It is offered as a public reference point for what named recipients + verifiable deliverables looks like in the same environment.
NNT · COZ PoW 2.5This section indexes specific, publicly-sourced governance concerns that surfaced across 2026. It intentionally covers actions taken by multiple actors. Where a concern involves a specific person, the criticism is of the documented action, not the person; the citation link takes the reader directly to the primary source. Additional documented concerns from the NF/NGD historical record — pending the deeper research flagged in the "Historical Deployment" research todo above — will be added here as they are researched with the same rigor.
Erik's own language — what he refused to disclose
On the 106,540 NEO ($300k) confidential expenditure: "The details cannot be disclosed at this stage because the matter is still in progress. Premature disclosure would not improve accountability; it would damage Neo's interests."
On the committee roster: "I do not want a second person to be pushed to the front line and subjected to political persecution, personal attacks, or pressure simply because they helped keep Neo running."
On staff identities: "No normal company or organization in the world is expected to publicly disclose the identities of its employees simply because salaries are paid from its operating budget."
On lone responsibility: "Before the situation improves, I am willing to take all public responsibility myself. If the community wants to question these temporary actions, question me."
On the end-state: "The end state should not be 'Council control' or 'founder control.' The end state should be community-authorized, on-chain governance."
Da's #4526 is the only proposal that targets the meta-lock directly. Mechanism: transfer non-reserve tokens to a 4-of-5 multisig Giveback II Lock Address controlled by initial Board directors, then execute a protocol-level rebasing to redistribute proportionally to holders.
Requires: NEO made divisible (for fractional withdrawal), exchange custodial support (for on-exchange holder credit), Board formation before Lock Address is armed. Timeline: 3 months for Lock Address, 6–9 months full execution.
This is the only mechanism in any of the three founder proposals that changes who holds voting NEO — not just who signs for it.
The $300k question. What did the 106,540 NEO "confidential infrastructure-related expenditure" actually spend on? Erik has committed to disclosure "after the underlying process is successfully completed." Track and update this section when disclosure lands (or when a specific deadline passes without one).
On-chain analysis of NF wallet movements over 12 months. Reconstruct the full flow of NEO/GAS from NF and NGD wallets across 2025–2026. Cross-reference with transparency portal disclosures. Would surface any unattributed transactions and validate (or challenge) the $1.2M total.
The affirmative case.
Data supply, not runtime.
Neo already ships the only major-L1 stack combining a protocol-native oracle, decentralised storage (NeoFS) priced in the host-chain asset, hard finality (dBFT 2.0), and a consumption dual-token model. That combination is directly relevant to the segment autonomous decision systems need: verifiable data supply. The rest of this tab is the case for building there.
Neo becomes the verifiable data-supply layer for autonomous decision systems — capturing $6.5M – $255M/year in GAS burn from prediction markets, DePIN, content provenance, and RWA infrastructure.
Enforcement began August 2, 2026. Requires provenance disclosure on AI-generated content. Creates forced market demand for verifiable anchor infrastructure. C2PA spec leaves the anchor layer open. 6–12 month window before Big Tech builds proprietary alternatives.
HIGH confidencePrediction markets ($1T by 2030 · Bernstein), DePIN ($100–200B by 2030 · Messari), content provenance (EU-forced), RWA data infrastructure ($2–3T by 2030 · BCG). All four require the same primitive: verifiable, on-chain data supply priced in a consumption asset.
MEDIUM confidence · analyst consensusChainlink (oracle only). Filecoin (storage only). Ethereum (runtime, no native oracle/storage). Solana (speed, no native oracle/storage). No major L1 ships all four primitives natively, priced in the host asset. Neo already does — quietly, mostly by accident.
HIGH confidence · verifiableThe stack that matters for data supply already exists on Neo, in production, priced in the same asset that secures the chain.
- Oracle — protocol-native. Not a bolt-on middleware. Called directly by smart contracts.
- NeoFS — decentralised storage priced in GAS. Same asset as compute + oracle + service invocation.
- dBFT 2.0 — hard deterministic finality. Reorg-resistant. Data anchored here is anchored forever.
- Dual-token consumption model — NEO is governance/capital; GAS is usage. Adoption = burn = holder accrual.
Every autonomous decision system needs an oracle, storage, finality, and a way to price consumption. Neo has all four, integrated, native, priced in one asset. This isn't a pitch — it's an inventory.
Weighted rubric from strategic outlook: TAM 2031 (total addressable market by 2031, 1×) + time-to-revenue (1×) + regulatory tailwind (1×) + Neo architectural fit & competitive whitespace (2×). Rationale for 2× weighting: a mid-cap L1 wins where architecture matters, not where distribution matters. Full methodology in Tab 3 · Market Research.
| Rank | Segment | TAM 2031 | Regulatory pull | Neo fit + whitespace (2×) | Score |
|---|---|---|---|---|---|
| 1 | Provenance / C2PA anchoring | Emerging (EU-forced) | HIGH | Zero commercial impl today · greenfield | 9.4 |
| 2 | DePIN storage-integrated | $100–200B (Messari) | MED | NeoFS-native · defensible vs Solana | 8.9 |
| 3 | Prediction market venue | $1T by 2030 (Bernstein) | MED | Oracle-native · dBFT finality | 8.6 |
| 4 | AI agent compliance infrastructure | Speculative | HIGH | Oracle + storage + audit trails | 8.2 |
| 5 | Enterprise-ML provenance | Growing (partner-driven) | MED | Storage + oracle + BD-driven | 7.9 |
| 6 | RWA data infrastructure | $2–3T (BCG) | MED | Partner-driven; legal-complex | 6.8 |
| 7 | Modular / interop | Broad | LOW | Distribution-dependent | 5.4 |
| 8 | Consumer / creator chains | Broad | LOW | Distribution-dependent | 4.7 |
| 9 | Gaming | Broad | LOW | Distribution-dependent | 4.2 |
| 10 | Custody + tokenized funds | Growing | MED | Institutional; slow build | 4.0 |
| 11 | Stablecoins (GENIUS/MiCA) | Large | HIGH | Incumbents entrenched | 3.6 |
| 12 | On-chain AI agent runtime | Speculative | LOW | Distribution war · Da's SpoonOS bet | 3.2 |
All five finalists — provenance, DePIN, prediction markets, agent compliance, enterprise-ML — require the same thing: verifiable data supply on Oracle + NeoFS + dBFT priced in GAS. That convergence is why the thesis is stated in supply terms, not in vertical terms. Neo doesn't need to pick one segment. It needs to build the primitive that all five demand.
Content provenance ranks #1 because the market is being created by regulation — not by hope. EU AI Act Article 50 enforcement began August 2, 2026. Every AI-generated image, video, and text destined for EU consumers requires provenance disclosure. The C2PA spec (Adobe/Microsoft-led) defines the metadata format but leaves the anchor layer open.
Neo's fit: dBFT 2.0 = tamper-proof anchor. NeoFS = decentralised storage for the manifest. Oracle = cross-chain publish. GAS = per-anchor pricing. Zero commercial implementations exist today. A greenfield market with regulatory pull is the wedge Meteor cannot rank first because Meteor's composition doesn't include anyone tracking EU regulatory calendars.
Time budget: 6–12 months before Big Tech (Adobe Firefly, Google, Microsoft) builds proprietary alternatives that become the default.
| Regulatory pull | 9/10 |
| Technical defensibility | 8/10 |
| Competitive whitespace | 10/10 |
| Time-to-revenue | 6/10 |
| Distribution requirement | 5/10 |
| Case against | Identity incumbents own the human end-user layer; agent-runtime narrative may crowd narrative bandwidth |
Quarterly gates 2026 Q4 → 2028 Q4, plus thesis-level direction 2029–2031. Every quarter carries publicly-declared go/no-go conditions and governance-accountability triggers. Missing a gate triggers formal wedge re-derivation, not silent continuation.
- Operational body constituted (with named accountable executive)
- Funding envelope declared ($17–25M total, phased)
- C2PA protocol spec landed as public engineering RFC
- C2PA anchor smart contract in production on N3
- Two pilot partners signed (one publisher, one AI vendor)
- NeoFS integration for manifest storage
- EU regulatory bridge (Numbers Protocol, C2PA consortium)
- Prediction market venue: 1 partner integration
- DePIN storage BD: 2 pipeline conversations to production
- C2PA anchor volume > 1M anchors/month
- Diversified segments (provenance + one of DePIN/prediction/agent-compliance) revenue-live
- Independent audit of accountability structure published
| Scenario | Data-supply market share | Est. 2030 GAS burn / year | Assumptions | Confidence |
|---|---|---|---|---|
| Low | 0.5% | ~$6.5M / year | Only C2PA anchoring materializes; DePIN and prediction segments miss | HIGH |
| Base | 1.5% | ~$50M / year | C2PA + DePIN storage + one prediction integration; agent-compliance emerging | MEDIUM |
| High | 5% | ~$255M / year | All 4 segments live; C2PA becomes standard anchor; RWA data begins to contribute | SPECULATIVE |
If any of these hold true by the stated dates, the thesis is wrong and the report will say so.
C2PA anchor demand fails to materialize. Fewer than 100k on-chain anchor transactions across all chains combined by end of Q2 2027.
Big Tech ships a proprietary alternative. Adobe, Microsoft, or Google ships closed-source C2PA anchoring that captures majority publisher share before open-source arrives.
EU Article 50 enforcement weakens or delays. Regulatory pressure drops such that publishers face no enforcement consequences for missing provenance.
Governance preconditions unmet. No accountable operational body exists; no named executive; no funding envelope declared.
No traceable GAS burn from data ops. On-chain instrumentation shows no attributable revenue from oracle calls, NeoFS storage, or anchor smart contracts.
Neo primitives deprecated or replaced. Any of Oracle, NeoFS, dBFT 2.0 is deprecated, forked away, or replaced by a non-native alternative.
Every phase gate above assumes a functioning execution layer. Today, that layer does not exist. Neo does not have a named executive with authority to ship. The Council cannot reach quorum. NF holds 41.2% of supply and appoints the Committee. The whitepaper's §8 names the specific preconditions any product thesis depends on and is honest about which are achievable. The thesis assumes governance reform. Without it, the thesis has no vehicle.
C2PA adoption tracker. Monthly refresh — publisher adoption count, cross-chain anchor volume, Big Tech proprietary alternative status, EU enforcement action count. Trigger for falsification criteria 1, 2, and 3.
Regulatory landscape deep-dive. Full write-up on MiCA implications, GENIUS Act, HK SFC, Singapore MAS — how they shape the data-supply market and Neo's positioning. Referenced in the whitepaper but not fully expanded here.
Twelve segments, scored.
Convergence on one primitive.
An independent 5-year market survey conducted as a peer artifact to Meteor's Phase 0. Twelve blockchain segments were surveyed against public sources (Bernstein, BCG, Messari, Pew Research, EU AI Act text, Chainlink Ecosystem reports, and category-specific analyst coverage). A weighted rubric was applied. The top-five finalists converge on the same underlying primitive: verifiable data supply.
Each area receives a 1–5 score on five dimensions. The last two dimensions carry a 2× weight.
Reason for the 2× on architectural fit and competitive whitespace: a mid-cap L1 with limited BD headcount cannot win a distribution war against Coinbase, Circle, BlackRock, or Solana Foundation. It can only win where architecture matters enough to overcome distribution disadvantage. A huge TAM with no defensible edge scores lower than a smaller TAM where Neo's primitives create genuine advantage.
Full per-row justifications and inline citations for the twelve-segment ranking are held in the underlying research corpus; available on request.
| Dimension | Scale | Weight |
|---|---|---|
| TAM 2031 (total addressable market) | 1–5 (1=<$10B, 5=>$500B) | 1× |
| Time-to-revenue | 1–5 (5=within 12mo) | 1× |
| Regulatory tailwind | 1–5 (5=regulation forcing adoption) | 1× |
| Neo architectural fit | 1–5 | 2× |
| Competitive whitespace | 1–5 | 2× |
| Weighted maximum | 35 | |
Twelve areas surveyed plus three sub-category breakouts where a landscape section flagged materially different sub-scores (Verifiable data has two sub-categories; Gaming/prediction markets is split). Score = TAM + T-t-R + Reg + 2·Fit + 2·Whitespace.
| # | Area / sub-area | TAM | T-t-R | Reg | Fit ×2 | White ×2 | Score | Evidence anchor |
|---|---|---|---|---|---|---|---|---|
| 1 | Verifiable data / provenance / C2PA anchoring | 3 | 4 | 5 | 5 | 5 | 32 | EU AI Act Article 50 enforcement Aug 2 2026; anchor layer open in C2PA spec; no blockchain incumbent |
| 2 | DePIN — storage-integrated, new-project chain of choice | 4 | 3 | 4 | 5 | 4 | 29 | Only decentralized storage priced in same asset as compute; Solana+Arweave stack fragments payment across 2–3 tokens |
| 3 | Prediction markets — differentiated venue | 4 | 4 | 4 | 4 | 3 | 26 | dBFT + native Oracle avoids two-provider stack; category 80% CAGR (Bernstein $1T by 2030); Polymarket moat is liquidity, not architecture |
| 4 | On-chain AI agent compliance infrastructure | 3 | 3 | 4 | 4 | 4 | 25 | NeoID + Oracle + NeoFS + dBFT map to regulator requirements for auditable agent decisions; Story Protocol adjacent but not identical |
| 5 | Content provenance for enterprise ML/AI pipelines | 3 | 2 | 5 | 4 | 4 | 25 | Enterprise ML lacks cryptographic proof of lineage; NeoFS + Oracle + dBFT map; but 12–24mo enterprise sales cycle |
| 6 | Regulatory-native Asia niche (HK/SG settlement) | 3 | 2 | 4 | 3 | 3 | 21 | dBFT determinism plausibly appealing to regulators; no SFC/MAS relationship exists; Canton better positioned |
| 7 | General oracle / financial price feeds | 4 | 3 | 3 | 3 | 1 | 18 | Chainlink 59% + Chronicle 13% + Pyth 6% + RedStone; Neo oracle underutilized; no path to displace |
| 8 | RWA tokenization | 5 | 2 | 4 | 2 | 1 | 17 | Ethereum $16.2B + Solana $2.9B; no Neo RWA AUM; Anchorage/Securitize/Circle relationships are Ethereum-native |
| 9 | Stablecoin rails | 5 | 2 | 3 | 2 | 1 | 17 | Visa+Mastercard+PayPal+Stripe consortium in stealth; Neo has no issuer, no merchant integration |
| 10 | Consumer / social / creator chain (Neo X general) | 4 | 2 | 3 | 2 | 1 | 15 | Base $32T stablecoin volume; Neo X has no distribution partnership, no killer app, no stablecoin depth |
| 11 | General P2E gaming | 3 | 2 | 3 | 2 | 2 | 15 | Ronin + Solana + Immutable have volume + studios; Neo has no game |
| 12 | Identity — competing with Worldcoin / Civic | 3 | 3 | 2 | 3 | 2 | 15 | NeoID protocol-level is distinct but zero users, zero apps, zero institutional partnerships; regulatory hostility on biometrics is horizontal |
| 13 | Institutional custody / tokenized funds | 4 | 2 | 3 | 2 | 1 | 15 | 5-provider oligopoly (Anchorage, Coinbase, Fireblocks, BitGo, Komainu); OCC-charter path is capital-heavy multi-year |
| 14 | Modular / interop / restaking | 4 | 2 | 3 | 1 | 1 | 13 | EigenLayer 93.9% share; LayerZero 75% bridge share; Neo has no TVL to bootstrap restaking |
| 15 | Privacy tech (native build) | 3 | 1 | 4 | 1 | 2 | 13 | No ZK/FHE stack; 18–36mo + $50–100M to build; Aztec has $180M funding + mainnet |
Four of the five finalists share a common upstream capability — verifiable data supply + verifiable storage + verifiable finality, all priced in GAS. C2PA anchoring is verifiable-data-supply for content provenance. DePIN storage-integration is verifiable-data-supply for sensor networks. Agent compliance is verifiable-data-supply for regulator-auditable AI decisions. Enterprise ML provenance is verifiable-data-supply for training-data lineage. The fifth (prediction markets) is a specialized customer of the same primitive.
This is not coincidence — it is Neo's actual architectural distinctiveness (Oracle + NeoFS + dBFT + dual-token) mapping onto the specific market segments where architectural fit outweighs incumbent distribution.
Case for
- Regulatory pull: EU AI Act Article 50 enforceable Aug 2 2026; provenance disclosure mandatory for AI-generated content in EU market
- C2PA spec's anchor layer is deliberately open; no blockchain has claimed it authoritatively
- Neo's Oracle + NeoFS + dBFT map exactly to the anchor role
- Numbers Protocol is the only visible early C2PA-on-blockchain implementation and is not architecturally integrated
Case against
- Time budget is 6–12 months before Microsoft / Meta / Google build proprietary anchors that become default
- TAM (3) is provenance sub-category — conservatively $50–100B by 2031; smaller than aggregate oracle market
- Success requires actual BD relationships with model publishers, media platforms, and EU compliance auditors
Case for
- Solana DePIN stack fragments value across a project-specific token, Arweave for storage, and SOL for compute
- NeoFS (storage priced in GAS) + Neo compute (also GAS) collapses value into one token
- Sector market cap $19B 2026 → $200–500B by 2031 (Messari base)
- Positioning target: default chain for new-launch DePIN projects from 2027 onward, not displacement of Helium/Hivemapper/Grass
Case against
- Time-to-revenue (3) is 12–18 months to a flagship — Solana / Sui / Aptos ecosystem funds are courting the same pipeline now
- Requires BD team, NeoFS SDK work, and concessional GAS-subsidy programme — significant execution burden
- 12-month delay costs Neo the 2027 project cohort entirely
Case for
- Category at $24B combined monthly volume (Pew, Apr 2026); Bernstein projects $1T by 2030 (80% CAGR)
- dBFT deterministic finality is genuinely appropriate for market resolution — a reorg during settlement is unacceptable
- Native Oracle avoids the two-provider stack every other chain requires (chain + Chainlink/UMA)
- CFTC federal-primacy prevailed August 2026 (Kalshi NY order); framework clearer than 5+ years
Case against
- Polymarket owns the liquidity moat; moat compounds monthly; by 2028 acquisition costs are significantly higher
- Whitespace (3) is only via sub-niches (weather-linked, agent-driven, Asian regional)
- Venue-building requires MM relationships and a resolution-source relationship layer Neo does not have
Case for
- NeoID + Oracle + NeoFS + dBFT map to regulator requirements for auditable agent decisions
- Bittensor/Virtuals own runtime; Story Protocol owns agent-IP — but regulated agent compliance is unclaimed
- EU AI Act + MiFID II digital-agent provisions (expected 2027) create pull for auditable-agent infrastructure
Case against
- Time-to-revenue (3): 18–24 months given nascent regulatory requirements
- Best run as an extension of Finalist 1's provenance primitive, not a standalone bet
- Weaker independent existence than Finalists 1–3
Case for
- EU AI Act obligations on high-risk AI systems phase in through Aug 2026 — dataset transparency and lineage are named requirements
- NYT v. OpenAI, Getty v. Stability, and dozens of similar suits produce licensing-verification requirements
- Same primitives as Finalist 1 (Oracle + NeoFS + dBFT), applied to training-data manifests
- No cross-industry standard exists for anchoring training-data manifests on-chain today
Case against
- Enterprise sales cycles 12–24 months; realistic first flagship not before Q4 2027
- Requires SDK integrations for standard ML pipelines (Python/PyTorch/HuggingFace/S3), enterprise SLAs, SOC 2 / ISO 27001 on NeoFS storage nodes
- Lower urgency than Finalists 1–3
RWA tokenization (17) & Stablecoin rails (17)
Both max TAM (5) but score 2 on Neo fit and 1 on whitespace. The rubric intentionally punishes "huge TAM, no fit, no whitespace" — a mid-cap L1 with limited BD headcount cannot beat Coinbase, Circle, BlackRock, and the DTCC on relationships and licenses.
Consumer / social / creator (15)
TAM is real (4) but Neo fit is low (2) and whitespace is closed (1). Base has $32T stablecoin volume because of Coinbase's distribution; Neo has no equivalent.
General oracle / financial price feeds (18)
Chainlink 59% + Chronicle + Pyth + RedStone leave no whitespace. Neo's native Oracle is architecturally real but does not overcome Chainlink's network-effect moat on financial price feeds. The provenance sub-category is the correct oracle play; general price feeds are not.
Identity (15)
NeoID is architecturally distinct (3), but Worldcoin / Civic / Polygon-ID have distribution and Neo does not; biometric regulatory hostility is horizontal. If Meteor's Phase 0 recommends identity infrastructure (widely predicted), that recommendation should be evaluated against this row. The ranking says identity is a distribution-limited market where Neo has no distribution.
Restaking / interop / modular (13)
EigenLayer's 93.9% share + LayerZero's 75% bridge share + Celestia's DA share leave no room for a mid-cap L1 to enter without a TVL Neo lacks. Wrong shape for Neo.
Privacy tech, native build (13)
No native ZK/FHE stack; 18–36 months + $50–100M to build. Aztec has $180M and mainnet. Only viable Neo path is partnership (deploy Aztec on Neo X) — a downstream-of-Aztec position, not a leading one.
Because Finalists 1, 4, and 5 are the same architectural primitive applied to three customer segments (media platforms; regulated agent operators; enterprise ML teams), and Finalist 2 (DePIN) uses the storage half of the same primitive plus the oracle half, and Finalist 3 (prediction markets) uses the finality + oracle half for market resolution — the wedge decision is not "pick one of five". It is "pick the sequencing of five".
Whichever segment is picked first must be the one with the strongest regulatory tailwind and shortest time-to-revenue, because that generates the case studies and unit economics needed to sell into the slower-cycle segments. DePIN and provenance anchoring are the two candidates: DePIN scores +3 higher on time-to-revenue and equal on regulatory tailwind; provenance scores +1 higher on TAM. Tie-breaker is which category has a customer this quarter.
Neo's defensible position, stated once: a verifiable-data-supply layer built on Oracle + NeoFS + dBFT + dual-token, priced entirely in GAS, addressing sub-markets where architectural fit outweighs distribution moat. The customer segments differ; the primitive is one.
Rigorous methodology.
Structural role dynamics shape the output.
Meteor is Neo's product-strategy initiative, announced August 16, 2026. The methodology (weighted decision matrix, Delphi outlier review, public voting on category weights) is standard industrial engineering — sound as a process. What warrants scrutiny is the structural composition of the research team: the role overlaps between voter and executor, between editorial coverage and participation, and the presence of an unnamed research firm. This analysis is about roles, not personalities — the criticism is of the composition as a governance design, not of the individuals occupying the seats.
The author now holds one of the seats this tab audits. As of 2026-08-25, Council member deanragnarok ceded his Meteor Phase 0 research-team seat to the author (Dean's seat was originally taken up on behalf of NeoNewsToday). This composition analysis and the pre-registered predictions below were drafted before the seat transfer and are published as-is; they apply to the composition including the author's own seat. Being the "independent-of-founders analyst" this tab's remediation asks for (see "Meteor's Potential — If the Composition Broadens" below) is a good answer only if disclosed first — that is the reason for this line.
Field research + opportunity framing. Council-nominated research team maps blockchain market for next 5 years, evaluates candidates against shared criteria, produces ranked shortlist.
Lean strategy workshop. Defines business hypothesis, target customer, product/market definition, first sellable wedge.
Technical + product planning. Converts selected strategy into actionable roadmap the ecosystem can align around.
"What has been missing is a shared, explicit product direction the entire ecosystem can organize around." Meteor exists to move Neo "from ambiguous direction to clear, collective focus." Endorsers named: Erik Zhang (with code deployment), NGD, core developers, sponsored communities, "significant number" of Council members. Da Hongfei is not named.
NNT · METEOR ANNOUNCEMENTThe independent market ranking in Tab 3 followed the same 4-step discipline Meteor proposes (research → rank → wedge → roadmap). The rubric structure is broadly aligned: both approaches weight architectural fit and competitive whitespace above raw TAM. Meteor's process may — or may not — converge on the same top-5 finalists (verifiable data / provenance, DePIN storage-integrated, prediction markets, agent compliance, enterprise ML provenance). When Phase 0 output publishes, the two rankings can be compared directly. See Tab 3 · Market Research.
Whether a research process is credibly independent is a function of role composition, not motive. Four structural dynamics in Meteor's Phase 0 team warrant naming.
A research-team nominee is also editorial staff at the primary Neo-focused publication (NeoNewsToday). The publication's own coverage of Meteor's launch did not disclose that participation. This is a role-conflict pattern, not a claim about intent — an editorial voice covering an initiative the same voice is helping shape.
Another research seat is held by a leader of Neo Global Development (NGD). NGD is both the party helping score the ranked shortlist and the primary executor of whatever direction wins (via ecosystem funding and treasury deployment). Every scoring criterion is thus assessed in part by an organization whose future funding depends on which direction is selected. Not a motive claim — a structural conflict-of-interest observation.
A third seat is held by a core developer publicly associated with one of the two founders' technical direction. Whichever direction that founder favors is likely to receive higher "technical leverage" and "execution feasibility" scores because the prior work sits inside that direction. Again — structural, not motive.
A fourth research contribution comes from an unnamed research firm. Anonymity precludes methodology critique, prior-work benchmarking, or conflict-of-interest audit; there is no reputational stake for a bad recommendation.
Update 2026-08-25 (seat-stacking observation superseded): Earlier drafts of this dynamic named a seat-stacking pattern — the same publication (NNT) holding two seats via two Council channels (the participant-journalist via a partner Council slot; a second NNT-linked contributor via NNT's own Council slot). At Phase 0 start this is no longer accurate: the second seat was ceded to the author (see disclosure at top of this tab). NNT now holds one research-team seat; the second-seat concentration is resolved. The observation was true at nomination and is preserved here rather than deleted, because the fix came from a single Council member's individual choice, not from a structural safeguard.
The specific individuals in each seat and the Council-slot nomination path that produced them are held in the author's underlying research notes; this publication intentionally omits personal names in the panel body per its de-personalization principle. Readers who want to identify specific seats can request the source notes directly.
Given the composition dynamics named above, the Phase 0 output is expected to skew as follows. When the actual output publishes, this section will be updated with a convergence/divergence audit against these predictions — right or wrong, visibly and with equal prominence.
Why these predictions are still meaningful with the author now seated: they were pre-registered before the seat transfer, and they describe composition effects across the full research team — not the author's own vote. One seat of several is not the mechanism producing the predicted skews; the founder-proxy, executor-overlap, and editorial-participation dynamics do. If Phase 0 diverges from these predictions, that is the informative outcome — the audit runs the same either way.
- Ranked #1 or #2: Identity infrastructure (the shipped OneGate stack as vehicle) — favored by the technical-proxy seat (existing work), by the voter/executor seat (existing capability), and by editorial coverage; user-base sizing from the unnamed firm serves as external validation.
- Ranked #3–5 for optics: One or two "diverse" directions (DeFi revival, RWA, cross-chain via Neo X) scoring lower on "strategic fit" and "technical leverage" because those categories are shaped by seats favoring existing work.
- Not ranked / dismissed: Directions requiring cession of execution to independent teams. Directions focused on holder value capture, treasury oversight, or token economics — likely framed as "governance topics, out of scope for product."
- Language check: "Accountability" is expected to be largely absent from the Phase 0 output. "Execution", "feasibility", "roadmap" are expected. The word that would name who is responsible if nothing ships is expected to be absent — this is a claim about published output only, not about intent.
Meteor's four-step methodology is the most disciplined product-strategy process Neo has run publicly. If the Phase 0 research seat composition is broadened — an independent-of-founders analyst added, the unnamed firm identified, the participant-journalist role addressed with disclosure or recusal — the same methodology can produce a genuinely credible ranked shortlist. The methodology critique is not that the process is wrong; it is that a sound process with narrow input composition produces a narrow output regardless of process quality.
A convergence between a broadened Meteor Phase 0 and the independent ranking in Tab 3 would be significantly more load-bearing than either alone. Both processes converging on verifiable data supply — because both were run by people with distinct incentive structures and both reached the same primitive — is the strongest form of the claim.
| Dimension | Meteor | Independent Research (this report) |
|---|---|---|
| Methodology | Council-weighted decision matrix + Delphi review | Weighted rubric (TAM · time-to-revenue · regulatory · Neo-fit ×2) + confidence tiers |
| Research team | 4–5 nominees · 2 founder proxies · 1 participant-journalist · 1 anonymous | 1 independent NEO holder · 60+ cited sources · all attributed |
| Sources | Anonymous firm + insider ecosystem sources | Public primary sources · analyst consensus with confidence tiers |
| Diagnosis | Missing product direction (strategy gap) | Missing execution + accountability (governance gap) |
| Falsifiability | Not explicitly named | 6 named criteria that, if unmet by dates, prove the thesis wrong |
| Funding | Council-blessed + NGD participation | Self-funded · no Neo entity grant · no fundraising |
| Accountability for the report | Distributed across research team + Council votes | One named author · own the reframes · take the exposure |
| Publication timing | Phase 0 output TBD (weeks) | Whitepaper drafted; publishes on next governance salience moment |
Meteor Phase 0 output — full analysis when published. Populate the convergence/divergence tracker above. Update the composite prediction score (were we right?). Publish comparison whitepaper if divergence is material.
Ten months of the governance crisis
October 2025 to August 2026. 25+ dated events across governance, founder dynamics, treasury, Meteor initiative, and strategic positioning. Filter by category. Every entry links to a public source.
Exchange delisting/listing correlation with governance events. Overlay major exchange decisions on the timeline to test hypothesis that governance instability drives listing changes.
Price correlation with governance turning points. Populate NEO/GAS price at each timeline entry. Would surface which events the market actually noticed vs. which were community-only signals.
Every claim traces to a public source
Methodology, confidence tier definitions, primary source index, and version history. This tab exists so any journalist, analyst, or holder can trace any claim in the report back to its origin — and challenge it.
- Tier 1 · Primary data: On-chain state, GitHub proposals, official announcements, dated financial reports. All quoted with URL + retrieval date.
- Tier 2 · Named analyst: Bernstein, Messari, BCG, CoinDesk, industry press with named author + date.
- Tier 3 · Trade press: NeoNewsToday, BlockchainReporter, Chainwire — narrative-only sources, cross-checked.
- Tier 4 · Journalist / VC opinion: Op-eds, panel talks, VC blog posts — framing-only, no citation weight.
Separate from confidence tiers (which ask how sure are we?), each material claim is being tagged with an epistemic type — what kind of claim is this?. Tags are being rolled out iteratively across panels; the most load-bearing claims carry them first. Where a claim carries no tag, treat it as a sourced claim by default and check the adjacent source chip.
Governance proposals (GitHub)
- · #4526 — Da Hongfei · Foundation Restructuring · 2026-04-09
- · #4531 — Erik Zhang · Governance Restoration · 2026-04-13
- · #4532 — Malcolm Lerider · Consolidate Assets · 2026-04-13
- · Issue #233 — Transparency portal critique · Erik's response · Malcolm's reply
- · #4411 — deanragnarok · STB proposal
- · #4467 — Erik Zhang · Staking / voting reform
Official announcements & press
- · NNT · Meteor initiative announcement · 2026-08-16
- · NNT · Erik OneGate vision · 2026-08-14
- · NNT · Da Humanless Blockchain op-ed · 2026-03-03
- · NNT · SpoonOS announcement
- · NNT · Neo 2025 Financial Report ($461M treasury)
- · NNT · COZ PoW 2.5 · same-period disbursement comparator
- · CoinDesk · Single-sig custody · 2026-04-16
- · Yahoo Finance · Neo founder fallout summary
- · Blockmanity · Neo blockchain shaken
- · BlockchainReporter · SpoonOS $2M fund
- · Chainwire · SpoonOS launch
- · Business Wire · Onchain Custodian (Da as Chairman)
Comparable-chain precedents
Underlying research corpus
This publication is anchored to an underlying research corpus held by the author, containing: primary-source captures of the three governance proposals (#4526, #4531, #4532); the transparency-portal thread and Erik Zhang's response to issue #233; Da Hongfei parallel-ventures reference material (SpoonOS, AEON, Onchain Custodian, Neo X); the OneGate direction reference; Meteor announcement and NNT coverage captures; the underlying whitepaper draft; the Meteor-parallel strategic-outlook workings; and analytical notes on participant motives and Meteor team profiles.
This publication cites only public, independently verifiable sources. Every substantive claim is anchored to a linked source visible where the claim appears. The underlying corpus is available on request for reviewers, analysts, and journalists.
Malcolm Lerider. NEO holder since 2016. Left the ecosystem in 2018 due to internal misalignment. Re-engaged in 2025 to make one more honest attempt at surfacing what he believes is the actual opportunity — and the actual blockers.
- NEO holder — position size not disclosed, materially exposed to price outcomes.
- Meteor Phase 0 research-team seat — ceded to the author by Council member deanragnarok on 2026-08-25 (Dean's seat was originally taken up on behalf of NeoNewsToday). No other institutional affiliation with any Meteor participant, Neo Council seat, core dev team, or Neo ecosystem project.
- No NGD grant, no Foundation grant, no ecosystem funding. Self-funded research.
- Engaged with both founders directly. Aligned with neither.
- Contributes public criticism of both Da/NGD's opacity and Erik's temporary committee spend.
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-08-25 | Interactive HTML report first release · pulls from whitepaper §1–§11, participant motives, Meteor composition, timeline |
| — | 2026-08-21 | Whitepaper §9 (meta-lock) added |
| — | 2026-08-17 | Whitepaper repositioned as "The Independent Case for the Data-Supply Layer" · strategic outlook published |
| — | 2026-08-16 | Independent research initiative launched · public intake via X + Discord |
This publication updates on material governance events: Meteor Phase 0 publication, founder announcements, Council votes, material treasury disclosures. Placeholders visible for charts (16) and research directions (11) not yet completed — those are features, not TODOs-in-code. This is a living publication.
Recommendations by audience
Four audience-specific recommendations. Each is calibrated to what that audience can actually do — hold, contribute, report, or vote — and each is designed to test the report's claims against future events. Where a recommendation depends on a specific piece of information becoming public, the trigger event is named.
Watch the custody transition milestone. The Dec 2025 financial report committed NF to a multi-sig migration without a dated milestone. The single most load-bearing governance improvement Neo can make is publishing that dated milestone. Absent that, everything downstream sits on the same base.
Watch the historical treasury disclosure. The 2025 report is the first comprehensive disclosure since H1 2020. A 2020–2024 comparable-granularity backfill (recipient lists, program outcomes) is a leading indicator of whether the disclosure discipline is durable or one-off.
Watch the $300k confidential line. The temp committee's May 18 line ($301k for "confidential infrastructure-related expenditure") is one that has committed to disclosure once the underlying process completes. Set a Q4 2026 reminder. If no disclosure lands by year-end, the pattern of unmandated authority not resolving into transparency is confirmed.
Watch what proposal #4532 becomes. As originally scoped, asset consolidation changes who signs, not who holds. Track whether it evolves to include redistribution or dilution mechanics — that is the meta-lock exit.
Compare the rankings. When Meteor Phase 0 publishes its ranked shortlist, compare directly against the independent ranking in Tab 3. Convergence is load-bearing signal. Divergence is diagnostic — it indicates which composition assumptions changed the answer.
Independent research intake is open. If you:
- Held NEO or GAS for >3 years and have opinions about founder patience
- Built something on Neo and left, or tried and gave up
- Are currently building on Neo and can speak honestly about what stops shipping
- Sit on a Council seat and can speak candidly (attributed or anonymous)
- Left the ecosystem (founder, employee, community lead) with a story that matters
Video call preferred, audio-only fine, written responses accepted. Attribution options: named, initials only, "council member," fully anonymous. Every quote sent back for approval before publication.
Press pack: This report + the underlying whitepaper (drafted, 137 KB, 11 sections, 60+ inline citations) + primary sources are available for reference. Every claim in this report traces to a public source via source chips.
Quote approval: Every attributed quote from an interview will be pre-approved by the speaker. Malcolm's own quotes are on record unless specifically flagged.
Questions worth asking — applied evenly across parties:
- To Meteor's organisers: publish the full research team roster with disclosure of the nomination path for each seat, and identify the unnamed research firm.
- To the Neo Foundation: publish the dated milestone plan for the multi-sig custody transition committed to in the Dec 2025 financial report.
- To Neo Global Development: publish a comparable-granularity 2020–2024 historical treasury deployment (recipient lists, program outcomes, investment portfolio detail) to match the 2025 report.
- To Neo Foundation: publish clear ownership of the early Binance investment, including intended destination of any liquidation proceeds.
- To the temporary committee: publish the roster, published headcount, and the underlying-process definition that determines when the $301k "confidential infrastructure" line can be disclosed.
- To Da: whether Neo X is a Neo initiative or an initiative operated by other legal entities — and if both, what funding-decision mechanism applies.
- To any Council seat whose voting record shows no participation in recent proposals: what the seat is for.
The report is open to correction. If a claim is wrong, a chart placeholder should be a different shape, or a section is missing an actor — file it. Attribution optional.
What's genuinely useful right now:
- Council voter turnout data — proposal-by-proposal seat participation across N3 lifetime
- Historical NGD grant outcomes — recipients + delivered revenue + attributable GAS burn
- Neo primitive adoption metrics — Oracle calls / month, NeoFS storage size, dApp counts
- Comparable-chain governance case studies — how Solana / Cosmos / Ethereum resolved similar structural problems
- Pre-Meteor architectural memos — internal documents on OneGate, SpoonOS, Neo X positioning
Contact: DM Malcolm on X (@MalcolmLerider) or Discord (mlerider). Corrections logged publicly with attribution unless you ask otherwise.
Neo has the stack. The market is real. The founders built something worth continuing. What we don't yet have is an accountable execution layer — and until we do, the shortlists will pile up and the code will not ship. This report exists to make that visible.
— Malcolm Lerider · Aug 2026