Technical Architecture: The Intelligence Stack
Miko's intelligence is not a single model responding to prompts. It is a production system composed of specialized layers, each engineered for a specific function in the pipeline from raw data to on-chain execution. This section details each layer — what it does, how it works, and why it matters for holders.
Architecture Overview
Layer 1: Data Ingestion and Semantic Filtering
The first layer is the system's sensory apparatus. It connects to the Twitter API, on-chain data sources, and — for the chain's tokenized equities — traditional equity market data feeds (Finnhub and Yahoo Finance) to collect raw information in real-time. It also ingests a curated smart-wallet feed: the on-chain buys and sells of proven Robinhood Chain traders. Unlike social data, wallet events are not taken at their word — each one is verified against the chain itself (the transaction receipt must show the exact token moving to the exact wallet) before it can influence anything downstream.
Raw data is not useful data. This layer applies NLP-based analysis and heuristic rules to:
- Filter noise — remove irrelevant content (non-crypto, spam, duplicate information)
- Score relevance — evaluate each data point for uniqueness, community relevance, and potential engagement
- Classify content — categorize by topic (DeFi, memecoin, infrastructure, etc.) and sentiment (positive, negative, neutral)
- Cluster related discussions — identify when multiple KOLs are discussing the same topic independently, using HDBSCAN clustering on TF-IDF vectors and embedding similarity
The clustering is critical for the fact-checking pipeline downstream. When three independent KOLs make the same claim, it carries different weight than a single source making a claim that nobody corroborates:
Where is the count of independent sources making the claim and is the power law exponent derived from social media attention distribution (Newman, 2005).
Layer 2: Knowledge Graph and Multi-Source Fact-Checking Engine
This is the layer that most fundamentally differentiates Miko from other AI agents.
Knowledge Graph
Miko does not treat each piece of information as isolated. Instead, it integrates data into a structured Knowledge Graph stored in proprietary database with vector embeddings for semantic search. This graph maps relationships between tokens, KOLs, market events, and projects. When Miko encounters new information about a token, it retrieves all relevant context — past performance, associated KOLs, historical claims, and verification status — enabling informed decisions rather than reactive responses.
The semantic search capability uses cosine similarity on embedding vectors:
Results above the configured importance threshold ( by default) are surfaced as contextual grounding for both content generation and asset selection.
The Fact-Checking Pipeline
Most AI agents in the crypto space process LLM output directly — what the model generates is what gets published or acted upon, with no independent verification step. When such agents control financial actions (trading, liquidity provision, token deployment), the cost of unverified information becomes real capital loss.
Miko's Fact-Checking Engine is a four-stage adaptive pipeline that consults six independent verification providers:
Key design decisions:
- AI-driven strategy selection: The verification level is not hardcoded. The AI evaluates each claim's characteristics (specificity, importance, independent source count) and decides how to verify it, selecting both the intensity and the specific providers whose strengths match the claim type.
- Adaptive fallback: If a provider fails (API error, timeout), the system excludes it and re-plans the strategy with remaining providers. Up to 2 additional attempts. Temporary outages never block verification.
- Evidence convergence requirement: A claim is verified only when evidence from independent sources converges on the same conclusion. Divergent evidence or insufficient data results in a "not verified" verdict.
- Specificity-aware evaluation: The synthesis stage checks whether specific details (names, numbers, dates, amounts) match the evidence, not just the general topic.
Where Fact-Checking Is Applied
The pipeline operates at three independent checkpoints:
For holders, this means: Information that feeds into Miko's asset selection has been subjected to multi-source verification. In a market where a single fabricated announcement can move a token's price dramatically, this verification layer is what stands between the holder's allocation and a selection based on false information.
Layer 3: Persona-Driven Generation Core
This layer creates Miko's voice: the public-facing content on X (Twitter) that drives community engagement and growth.
Multiple reaction modes allow Miko to respond dynamically to different situations — from cheerful curiosity for friendly exchanges to sharp wit for provocative interactions to analytical depth for market discussions. These modes are not random; the system evaluates the conversational context and selects the most appropriate response style.
Beyond conversational content, the Generation Core publishes structured market reads: when a token takes over the top of MIKO's attention board, Miko posts a curator's read — what is actually carrying the move, what kind of table it is, and the specific on-chain meter that decides where it goes next. These reads are grounded in the analyst layer's measured facts (including observed holder-structure data) and always end on the watch-point, never on a verdict — Miko is a curator, not a trading-signal account.
Every response Miko generates is verified for originality before posting. The system ensures content is genuinely Miko's own expression, not a mechanical repetition of source material. This is enforced through multiple independent verification layers at the code level.
Miko's persona is also published as an open model: a fine-tuned open-weights release on Hugging Face and Ollama that carries her voice in the weights themselves, callable through the live REST API and MCP server. See Open Model.
For holders, this matters because: Miko's social presence is the primary driver of community growth. Community growth drives trading volume. Trading volume generates tax revenue. Tax revenue funds the weekly acquisitions. The quality and authenticity of Miko's social output directly impacts the size of the weekly acquisition treasury.
Layer 4: Selection Algorithm
This is the financial brain of the protocol. It runs two decision streams — the weekly core selection that determines what the core sleeve buys, and the continuous attention-leader tracking that steers the satellite sleeve. It is the most critical component for holder allocations and the most technically sophisticated.
The Model Tournament: Three Phases, One Live Seat
The Selection Algorithm is built as a live tournament between competing models. Three statistical phases — each a real model family requiring progressively more data — enter the tournament as training data accumulates, and the weekly core selection is always made by the current champion.
How the seat is decided:
- Blind predictions first. At each weekly selection, every entrant scores the same frozen candidate view, and its complete ranking is recorded before any outcome exists. Predictions are immutable — there is no backscoring.
- Outcomes as the judge. When a selection group's 7-day outcomes are complete, each entrant is scored by the Spearman rank correlation between its recorded ranking and the candidates' realized 7-day returns — every entrant against the identical candidate set and identical labels.
- The champion is the cumulative leader. The live selector is whichever entrant leads the accumulated paired record. Promotion and demotion are the same rule in both directions: a model takes the seat by out-predicting the incumbent on the shared record, and loses it the same way. Both directions are automatic.
- Sequential entry. Phase 1 — a Bayesian linear return model fitted over the frozen candidate features, with its prior anchored to the deterministic baseline — enters as soon as the first complete training group exists. Phase 2 — Thompson sampling that draws one reproducible coefficient sample from the Phase 1 posterior per selection and scores all candidates with that same draw — follows. Phase 3 — CatBoost learning-to-rank with YetiRank loss, one ranking group per selection — enters as the dataset grows. Each new entrant competes from its first week: it is scored, not trusted.
- An honest history. When the evidence basis widened from attention alone to attention plus verified capital, the record was not rewritten. The earlier social-only models remain in the same records as reference benchmarks — scored on every selection group they can represent, visible alongside the current roster, but no longer eligible for the seat. The track record keeps its past instead of replacing it.
- The permanent baseline. The deterministic fusion scorer anchoring the roster is never retired. If no learned model can out-predict it, it simply keeps the seat — a floor under the whole system. Random selection and the chain's benchmark asset are recorded alongside the roster as reference floors, visible in the same records but never eligible for the seat.
The Deterministic Baseline: Attention Acceleration
The roster's deterministic anchor is a scorer built for one question: where is verified, independent conviction arriving right now? Its first axis is attention:
- Independent-author corroboration: selection input is KOL coverage with one vote per distinct author — an author's repeated posts collapse into a single voice, so posting volume cannot substitute for breadth. A minimum number of independent authors in the current window is required before a token is rankable at all.
- Persuasion-weighted support: each author's voice is weighted by the persuasion score of their posts, so reasoned conviction counts more than reflexive hype, and low-persuasion noise shrinks toward zero.
- Acceleration, not level: support is measured against the token's own trailing 7-day baseline. A token that has been loud all week must keep exceeding its own normal to stay on top; a quiet token that suddenly draws broad, persuasive attention registers immediately.
The Second Evidence Axis: Verified Capital
Attention tells the system what the market is saying. Since the multisignal upgrade, the scorer reads a second, independent axis: what a curated set of proven on-chain traders is doing with real money. The two axes are fused into one score — and the capital axis is engineered so that it corroborates attention without ever being buyable:
- Receipts, not reports. A wallet event enters the pipeline only after the chain itself confirms it: the transaction receipt must show the exact token transferring to the exact wallet. An unconfirmable event is held for review, never scored.
- One actor, one voice — on-chain too. Just as the attention axis counts one vote per distinct author, the capital axis counts one bounded unit per effective actor: wallets that can be linked are collapsed into a single cluster, and a cluster's contribution is the mean of its buys' time-decay weights, not the sum: