Inside Operation Meteor: The Council Member Voting Guide
by
COZ / Tyler Adams (Facilitator)
12 September 2026
A Walkthrough of Category Weighting, Consensus Mechanics, and Council Authority
Meteor is an open, structured Neo ecosystem initiative designed to assign market priority, align ecosystem resources, and establish unified strategic focus for Neo's growth over the next 5 years (2026–2031).
Meteor establishes strategic priority. Depending on Council scoring, there may be one or multiple target market opportunities prioritized for execution.
A continuous framework supporting periodic category re-weighting and new opportunity injection as market dynamics shift.
As a Neo Council Member, your seat holds the decision authority for establishing strategic category weights and scoring candidate market priorities.
Each Council Seat has distinct voting and review milestones during Phase 0:
Score the relative importance of 16 evaluation criteria on a scale of 1 (low importance) to 10 (critical importance). Scores are normalized across all 21 seats to establish canonical priority weights.
Review the 5 to 10 Market Opportunity Dossiers authored by the Research Team. Each dossier includes full market sizing, competitor benchmarking, Neo technology fit (dBFT, NeoFS, Neo X, SpoonOS), and structured category evidence.
A parallel 2-week voting window on the existing ecosystem/tech backlog using normalized weighted ranking to establish near-term engineering priorities.
Participate in periodic cycles to re-weight criteria or evaluate newly injected market opportunities as ecosystem conditions shift.
Strictly 1 Council Seat = 1 Ballot / 1 Vote. Total 21 seats (NGD holds 3 seats; all other organizations/nodes hold 1 seat each).
In-progress votes are kept strictly confidential by the Facilitator to prevent anchoring, lobbying bias, or band-wagoning.
Every category is scored 1 (Weakest / Least Favorable) to 10 (Strongest / Most Favorable). Higher scores indicate higher priority/fit.
No candidate market is pre-eliminated by technical vetoes. All candidates are evaluated fairly and holistically on the full matrix.
Below is the complete reference matrix of all 16 standardized evaluation criteria weighted in Vote 1. Council members evaluate each category on a 1–10 positive-direction scale, establishing the canonical weighting model for all candidate market opportunities:
| # | Category | Description (What It Tests) | Scoring Examples (Weak vs. Strong) |
|---|---|---|---|
| 1 | Right market timing (next 5 years) | Is this a good opportunity for Neo to pursue now, with a realistic chance to matter during the next five years (2026–2031)? |
Weak (1)
Market is fading, too early to support, or Neo arrives after the window has closed.
Strong (10)
Clear market opening now, with high relevance and growth sustained over the next 5 years. |
| 2 | Long-term staying power (10 years) | If the first version works, is the underlying need likely to stay useful, relevant, and adaptable for a decade? |
Weak (1)
Depends mainly on a short-lived trend, temporary incentive, or fleeting market cycle.
Strong (10)
Addresses a durable, foundational need that can evolve and expand for many years. |
| 3 | Strength of the problem | Does this solve a real problem that users or organizations care enough about to change behavior or spend budget? |
Weak (1)
Vague, minor, or mostly an internal ecosystem hope rather than a felt customer pain.
Strong (10)
Clear, painful, frequent, and important enough that customers actively seek an alternative. |
| 4 | Clear customer, buyer, and route to reach them | Do we know who uses it, who approves/pays for it, why they act now, and how Neo can practically reach them? |
Weak (1)
Users, buyers, and GTM routes are vague; relies on passive hope that someone will adopt it.
Strong (10)
Target user group, decision maker/payer, trigger to act, and distribution path are crisp. |
| 5 | Why Neo should do this | Does this direction leverage Neo's distinctive strengths (dBFT, NeoFS, Oracles, Neo X, SpoonOS) and reinforce Neo's position? |
Weak (1)
Any generic chain could do it identically; gives Neo no distinctive advantage or brand lift.
Strong (10)
Directly harnesses Neo's technical, governance, and brand strengths to create a clear home. |
| 6 | Ability to stand out and stay ahead | Can this become meaningfully differentiated and defensible rather than easy to commoditize or copy by L1s/L2s? |
Weak (1)
Looks like existing crowded offers with no moat; easily replicated or outspent.
Strong (10)
Clear structural reason to choose Neo; built-in stickiness and sustainable differentiation. |
| 7 | Believable way to make money | Is there an early, credible path to revenue, sustainable fee capture, or direct economic value creation? |
Weak (1)
No identifiable payer; relies on wishful future monetization or indefinite subsidies.
Strong (10)
Clear paying customer, high-value outcome, and believable ongoing value capture. |
| 8 | Ability to bring useful activity to Neo | Will this bring real recurring builders, users, partners, applications, and liquidity into the Neo ecosystem? |
Weak (1)
Isolated one-off project or announcement with little lasting ecosystem spillover.
Strong (10)
Creates repeatable incentives for outside developers, capital, and users to engage with Neo. |
| 9 | Speed to a useful first proof | Can a focused, lean team deliver something credible to test, show, or sell quickly without a multi-year program? |
Weak (1)
First proof takes years, requires a massive team, or depends on heavy unresolved dependencies.
Strong (10)
Small team can deliver a functional prototype, pilot, or initial validation within months. |
| 10 | Practical path to a real first product (MVP) | How realistic is it to obtain required non-code assets, licenses, capital, counterparties, liquidity, or audits for a real MVP? |
Weak (1)
Needs heavy external licenses, massive liquidity, or complex regulatory assets before a real MVP can exist.
Strong (10)
Required assets and conditions are accessible; normal product execution delivers a truthful MVP. |
| 11 | Can Neo build and operate it well? | Can the ecosystem realistically build, secure, operate, and maintain this with available or obtainable technical talent? |
Weak (1)
Relies on unproven tech, fragile architecture, unmanageable security, or implausible operations.
Strong (10)
Practical architecture, manageable security/ops, and credible engineering capability in place. |
| 12 | Manageable legal, trust, and reputation risk | Can Neo pursue this direction safely without severe compliance hazards or unmanageable reputational exposure? |
Weak (1)
Severe regulatory/legal hazards or forces promises the ecosystem cannot safely keep.
Strong (10)
Risks are well-understood, proportionate, and safely manageable through clean operating design. |
| 13 | Ability to learn quickly | Can Phase 1/2 rapidly test critical assumptions through user conversations, sales feedback, or small staged pilots? |
Weak (1)
Critical assumptions cannot be validated until after massive capital expenditure or long delays.
Strong (10)
Key hypotheses can be pressure-tested rapidly with real users, partners, and lightweight tests. |
| 14 | Useful future options | Does this direction open valuable strategic options and adjacent expansion paths even if the initial wedge pivots? |
Weak (1)
Narrow dead-end bet; if the initial concept misses, little reusable capability or learning remains.
Strong (10)
Builds reusable infrastructure, relationships, and market footholds that support multiple future paths. |
| 15 | A clear Neo story | Can the direction be explained simply, crisply, and convincingly as a logical Neo foothold to builders, investors, and users? |
Weak (1)
Feels random, confusing, or disconnected from what Neo stands for and is building toward.
Strong (10)
Inspiring, cohesive narrative that clearly articulates Neo's strategic rationale and role. |
| 16 | Market attention, hype, and token demand | Can this credibly generate organic attention, narrative pull, and structural demand for NEO and GAS? |
Weak (1)
Low narrative pull; depends on artificial promotion with no real connection to token utility.
Strong (10)
High-interest narrative with clear mechanics driving genuine ecosystem excitement and token demand. |
Formal launch of Meteor across the ecosystem. Alignment across all research, governance, and developer lanes.
2-week Council voting window to score the relative importance of the 16 decision criteria (1–10 scale). Facilitator normalizes votes into canonical weights.
Parallel Council voting window on the existing ecosystem and technical backlog to guide near-term engineering priorities.
Research Team sources global market trends, clusters community inputs, and authors standardized Market Opportunity Dossiers.
Research Team formally publishes 5 to 10 standardized dossiers for Council review and public community debate.
Council scores candidate dossiers across all 16 weighted categories (1–10 scale). Concurrently triggers near-term roadmapping and core developer activation.
Confidential outlier review cycle highlighting major score variance for Council discussion to explore disparate perspectives.
Final ballot adjustments submitted; Facilitator tallies weighted consensus scores and publishes final strategic priorities ecosystem-wide.
Prioritized market opportunities hand off into Product Definition Workshops, roadmapping, and Phase 2 developer execution.
Periodic reweighting cycles and candidate opportunity injection as ecosystem capabilities and global markets evolve.
To ensure complete clarity on Council seat obligations, please follow this operational checklist: