Skip to main content

OpenKaito

OpenKaito — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

OpenKaito — an AI/Inference | AI/Other project on the Bittensor network (Subnet 5), token (symbol: —).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: an open implementation for Bittensor Subnet 5 (“Decentralized Embedding”), focused on text‑embedding models.
  • Who it’s for: SN5 miners/validators and developers/integrators who need text embeddings.
  • Why onchain/token: onchain is needed as part of the Bittensor network (accounting/incentives in the subnet); a separate “necessity of a project token” is not established per Tier‑1.
  • What you can actually touch (Tier‑1): the quickstart guide for installing/configuring a validator/miner in the OpenKaito repository.

How it works (very briefly)

  1. Participants run subnet roles: miners and validators install the SN5 software per the quickstart.
  2. Miners do: train/deploy text‑embedding models and serve embedding requests.
  3. Validators do: evaluate the quality of the embeddings (benchmarks/comparisons) to incentivize improvement.
  4. Where the blockchain is: the subnet’s accounting/incentives are tied to the Bittensor network; the dynamics can be observed via the network dashboards (see links_*).
  5. Token role (if any): a separate project token is not established per Tier‑1; the Bittensor network has the native TAO token (a separate level).

Quick links: AI thesis fit

Project passport

Field Value
Project name OpenKaito
Also known as (aliases) Bittensor SN5; Decentralized Embedding
Logo (logo) ../assets/478_openkaito_logo.svg
Token symbol (ticker) —
Category AI/Inference | AI/Other
Primary chain (chain) Bittensor
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) —
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Per Tier‑1 it is not established whether a separate “project token” exists; incentives are described in terms of a subnet of the Bittensor network.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) text embeddings (model training/serving in subnet)
Use‑case (use_case) semantic search / NLP embeddings
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 0 / evidence_score 1
Last verified 2026-02-11

General project overview

OpenKaito (Bittensor Subnet 5), in its Tier‑1 repository, describes the goal of “Decentralized Embedding”: the development of text‑embedding models, where miners serve the models and validators evaluate quality on benchmarks. This provides a verifiable basis for the AI part (what exactly is done) and for the onchain part (the subnet as an element of the Bittensor network with incentives/accounting).

Features/modules

  • Quickstart/installation (Tier‑1): instructions for configuring a validator/miner (see links_*).
  • AI task (Tier‑1): text embeddings: training/serving of models and generation of embeddings.
  • Incentive mechanism (Tier‑1): the incentive mechanism and the role of validators in quality evaluation are described.

Typical scenarios

  • Scenario 1: a miner sets up the environment and runs a miner → serves embedding requests.
  • Scenario 2: a validator runs a validator → evaluates the quality of models/embeddings on tasks/benchmarks.
  • Scenario 3: an integrator obtains embeddings via the claimed “validator API” (the interface is claimed in the README; specific endpoints are not recorded in this card).

Getting started (wallet/network)

  • What you need: the quickstart in the repository (validator/miner setup).
  • Network/chain: Bittensor (Subnet 5).
  • Fees: depend on operations on the Bittensor network and the participant’s infrastructure (not calculated in this card).

Architecture/tech (non‑AI)

  • Components: the subnet codebase (repository) + the miner/validator roles and their infrastructure.
  • Participant roles: miners (training/serving of embedding models), validators (quality evaluation), users (access via the validator API).
  • Where logic runs: training/inference — offchain at the participants; accounting/incentives — on the Bittensor network.
  • Dependencies: GPU/infrastructure for training and inference serving (described in the README).

Token/economics (expanded, no forecasts)

  • Token utility: a separate “project token” is not established per Tier‑1; the economic part is described as the incentive mechanism of a subnet on the Bittensor network.
  • Protocol necessity drivers: the incentives and the roles of validators/miners are described in the README; at the same time, the TK flags regarding a separate token are set conservatively.
  • Who pays fees: depends on operations on the Bittensor network and the participants’ infrastructure (not detailed).
  • Where fees go: not established per Tier‑1 (in this card).
  • Issuance/burn: not established per Tier‑1 (in this card).
  • Security/incentive mechanisms: the incentive mechanism is described; the details of collateral/penalties (in terms of a separate token) are not extracted.
  • Distribution and token issuance schedule: not established per Tier‑1 (in this card).
  • Treasury: not established per Tier‑1 (in this card).

Governance

  • Who makes decisions: not established per Tier‑1 (in this card; changes are visible via the repository).
  • How protocol parameters change: changes are recorded in the codebase/commits (see links_*).
  • Where decisions are discussed/made: GitHub Issues/PR and the Bittensor Discord (see links_*).
  • Keys/multisig: not established per Tier‑1 (in this card).

Security and incidents

  • Audits: not established per Tier‑1 (in this card).
  • Bug bounty: not established per Tier‑1 (in this card).
  • Incidents: not established per Tier‑1 (in this card).
  • Threat model: risks of manipulation of quality evaluation/data and infrastructure risks of serving; the details require separate verification.

Project status and timeline

  • Current status: active (there is a repository and up‑to‑date instructions).
  • Key releases/milestones: the reference point is the commit history (see links_*).
  • Roadmap: the README has a “Development Roadmap” section (see Evidence).

Ecosystem/integrations

  • Integrations: not established per Tier‑1 (in this card, apart from the claimed “validator API” interface).
  • Partners: not established per Tier‑1 (in this card).
  • Where it’s actually used: claimed as access via the validator API; actual integration cases are not listed in this card.

AI component of the project

  • What is real AI here? training/serving of text‑embedding models; validators evaluate quality on benchmarks (Tier‑1 README).
  • What is truly onchain? the subnet operates within the Bittensor network with incentives/accounting; the dynamics can be observed via the network dashboards (links_*).
  • Why is a token needed? a separate project token is not established per Tier‑1; the economic part is described as the subnet’s incentive mechanism.
  • Red flags (based on the information found): the use of superlatives (“SOTA”) without a public table of metrics/versions; what to double‑check: the presence of the public dashboard/metrics from roadmap v1.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 sources describe a working AI‑oriented product (AI_1/AI_2/AI_4), so “intent without evidence” does not apply.
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): AI is already described as a function/task of the subnet being implemented, not only as a plan.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Subnet 5 trains and serves text‑embedding models (generation of embeddings for text).
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): The README explicitly describes the goal/task of the AI part and the participant roles.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a quickstart instruction for installing and running a validator/miner.
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito/blob/main/quickstart.md
  • Why sufficient / why not (one line): This is a reproducible “demo surface” (how to start and run the roles).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): The README says that validators use benchmarks, but Tier‑1 sources do not record a specific public table of metrics/versions/dates.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): There is a Tier‑1 repository with code, the project structure and documentation (README + docs/).
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito ; https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): The public code and documentation provide sufficient technical context.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Bittensor (Subnet 5)
  • Addresses/identifiers: Subnet 5 (SN5)
  • Evidence: Tier‑1 — https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): The README explicitly states that this is Bittensor SN5.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the subnet’s accounting/incentives and the interaction of the roles (miners/validators) within the Bittensor network.
  • Evidence: Tier‑1 — https://bittensor.com/whitepaper ; https://github.com/OpenKaito/openkaito/blob/main/README.md
  • Why sufficient / why not (one line): The mechanics of subnets and incentives belong to the network protocol, not to “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the Bittensor network, the trustless accounting of incentives and the verifiable distribution of rewards between the roles break down.
  • Evidence: Tier‑1 — https://bittensor.com/whitepaper
  • Why sufficient / why not (one line): The subnet relies on the trust model of the network and the onchain accounting of incentives.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): It is not established whether a separate “project token” exists; the fact of “no token” was not found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): We set TK_0=1 only with explicit proof of the absence of a token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No mechanism of “payment with a separate token for the embedding API” was found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit pay‑for‑service mechanism and a source.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): No collateral/penalty mechanism in terms of a separate project token was found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is the subnet’s incentive mechanism, but a separate token mechanism is not confirmed.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance mechanism via a separate project token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): 1 requires an explicit governance mechanism and a source.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token has not been assessed (the existence of a separate project token is not established).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Data on the token and its role are needed to discuss replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/OpenKaito/openkaito/blob/main/README.md Tier‑1 description of SN5: embeddings, the roles of miners/validators, the incentive mechanism and the roadmap.
Tier‑1 https://github.com/OpenKaito/openkaito/blob/main/quickstart.md What you can touch: the quickstart for installing a validator/miner (AI_2).
Tier‑1 https://github.com/OpenKaito/openkaito Public repository with code and docs (AI_4).
Tier‑1 https://bittensor.com/whitepaper Tier‑1 description of the Bittensor network and the mechanics of incentives/subnets (OC_2/OC_3).
Tier‑1 — No Tier‑1 source for claim “a separate project token is mandatory for pay‑for‑service / collateral / governance” was found.
Tier‑2 https://taostats.io/subnets/5/chart Observable dynamics of Subnet 5 (context; dashboard aggregator).
Tier‑2 https://www.coingecko.com/en/coins/openkaito Reference profile (context).
Tier‑2 https://coinmarketcap.com/currencies/openkaito/ Reference profile (context).

No comments to display

Back to top