Komodo ranks #154 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #1078: 924 of the 1077 assets ahead of it are not native coins but tokens or claims. A token is issued on a host blockchain rather than running its own; a claim stands for an asset already counted. Of the 1333 non-native assets CoinSpectrum lists above it by market cap, about 60% are tokens, 32% are claims on other assets, 7% are memecoins and 1% are NFT collections.
| CoinSpectrum Grade | A · 65/100 · provisional, B to A |
|---|---|
| Rank among cryptocurrencies | #154 |
| Rank counting claims | #1078 |
| Market capitalisation | $7M · a day's trading is under 0.001% of it: a quoted figure, not one holders could sell into |
| Price | $0.0484 |
| Circulating supply | 135,953,876 KMD |
| Maximum supply | no fixed cap |
| Consensus family | Proof of Work |
| Consensus mechanism | Equihash (200,9) |
| Own hashrate | 697 kH/s |
| Network purpose | Exchange chain |
| Ledger type | Single-asset ledger |
| Launch distribution | Presale |
Market figures from the 10 November 2026 build. Open the live view for every exchange's price, and charts.
A — 65 out of 100, provisional (from 10 of 10 sections, 10 November 2026 build). With what is not yet measured anywhere from nothing to full marks, the score would be 59 to 68 (B to A).
| Section and criteria | Score | Basis |
|---|---|---|
| Consensus | 10 | average of 2 criteria |
| By leader (its largest chain's market cap) (Source) | 10 | Proof of work: 10 of 10 on the ladder of consensus families ranked by their largest chain's market cap |
| By family (all its chains' market cap) (Source) | 10 | Proof of work: 10 of 10 on the ladder of families ranked by the combined market cap of their chains |
| Supply | 8.3 | the supply scale times 0.9, and a point for a fixed cap that holds |
| Supply (21 million scores 10) | 9.2 | no fixed maximum; 136 million in circulation |
| Distribution | 5.5 | average of 3 parts |
| Holder concentration (Source) | – | Not yet measured |
| Active addresses | – | Not yet measured |
| Premine (allocated at launch) | 2.9 | 71.1% of today's supply allocated at launch to founders, a company, a foundation or investors. All 100M KMD at genesis were pre-allocated: 90M sold in the 2016 ICO and 10M kept by the team. Against current supply of 140,660,565 (CoinGecko, 2026-10-23) that is 71.1%. source |
| Fundraising (share sold) (Source) | 3.6 | Sold by its issuer or insiders: 64% of supply sold. Public ICO from 15 Oct to 20 Nov 2016 raised 2,639 BTC (about $2M), with a 25% first-day bonus; coins were issued 31 Jan 2017. 90M KMD sold. source |
| Developer share (after launch) | 10 | No developer share: every new coin goes to the miners or validators who produce blocks. The block reward (3 KMD, cut to 1 KMD by KIP0002 in 2024) goes to miners, including notary nodes. The active-user reward paid to holders (5%, cut to 0.01% by KIP0001 in 2023) is not a cut, and there is no dev fund in issuance. source |
| Decentralisation | 6.7 | average of 3 parts |
| Governance (Source) | 10 | No authority can halt the chain or freeze funds: Elected notary nodes checkpoint the chain (dPoW) against deep reorganisations, but no party can freeze, blacklist or claw back ordinary users' coins. source |
| No central team (Source) | 0 | A central team directs it: The komodod reference client lives in the KomodoPlatform/komodo repository and is maintained by the Komodo Platform team, which also authors the KIP proposals. source |
| Who can mint (Source) | 10 | Open to anyone with hardware: anyone can produce blocks by mining, no permission needed |
| Nodes (Source) | – | Not yet counted |
| Security | 4 | 3.2 of 8 points source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | 0 | largest 50.7%, largest three 100% |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | 0 | about 54 transactions a day |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | 5.3 | own work 5; about 2.3 kW, 0.3 of 5; 0.0022% of its algorithm's largest, not scored |
| Clients (Separate code and teams 10, separate code or teams 9, a fork by the same team or a stale second 8; one client: a new version within 12 months 7, 24 months 6, none in 24 months 5, none in 48 months 3; a second in development +0.5, a second seen running +1, 8 at most with one client; chain ended 0; 1 point) | 7 | one client, latest version Oct 2026 |
| Open source (Node software) | ✓ | |
| No 51% attack (Nor a deep reorganisation, five years) | ✓ | |
| Scalability | 8.8 | average of 5 parts source |
| Fees ($0.001 or less 10, $1 or more 0) | 10 | typical fee $8e-7 |
| Throughput (2,478 a second, the busiest network's peak day, 10; 121, the median of the ten busiest, 5) | 7.5 | about 559 simple transactions a second |
| Block time (10 minutes 10, less either side) | 6.5 | a block every 1 minutes |
| Block space per 10 minutes (24 MB or more 10: the ten busiest networks' median demand, 16.4 MB, and half again for growth) | 10 | 8.39 MB limit, 80.5 MB per 10 minutes |
| Features (3 checks) | 10 | 3 of 3 passed |
| Fast payments (Safe to accept within seconds · Whitepaper abstract, §1, §2 and §11) | ✓ | The Zcash/Bitcoin-0.11-derived komodod rejects any mempool conflict ("Disable replacement feature for now"), i.e. first-seen relay with no replace-by-fee; blocks are about a minute apart, with dPoW notarisation on top. |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | ✓ | Komodo 0.9.2-3 keeps the inherited -prune option (deletes old blocks; disables the wallet). |
| Light clients (Payments verified from headers · Whitepaper §8) | ✓ | zcashd-derived node serves BIP37 merkleblocks for SPV checks of transparent payments. |
| Privacy | 8.7 | 8.7 of 10: whitepaper privacy 7 of 7, extra features 1.7 of 3, 1 not yet researched source |
| Protocol level privacy (Keys not tied to an identity · Whitepaper §10) | 10 | Addresses are hashes of keys users generate themselves; the node checks scripts and signatures, with no identity condition in its consensus rules. |
| UTXO ledger (Separate outputs, change to a new address · Whitepaper §2, §9) | 10 | Coins are separate unspent outputs: a payment spends whole outputs and sends the change to a new address, so the coins in one wallet need not share a history. |
| HD addresses (A new address for each payment, unlinked · Whitepaper §10) | – | |
| Hidden amounts (Amounts confidential) | 5 | Sapling shielded transactions remain valid on the KMD chain (privacy-only restrictions apply only to ac_private asset chains). Optional: 5 of 10. |
| Hidden parties (Sender and receiver hidden) | 5 | Sapling spends hide the sender and shielded addresses the receiver. Optional: 5 of 10. |
| Network privacy (Origin hidden by default) | 0 | Bitcoin-derived node relays its own transactions over clearnet by default; Tor (-proxy/-onion) needs user setup and there is no Dandelion. |
| Programmability | 4.4 | 4 of 9 points source |
| Token issuance | 0 | No token issuance on the chain itself |
| Smart contracts (Scripting for spending conditions) | 1 | Zcash-derived Script on the KMD chain; Antara cryptocondition modules are off on KMD itself (ac_cc 0). |
| Multisig and time locks (Without a third party) | ✓ | OP_CHECKMULTISIG and OP_CHECKLOCKTIMEVERIFY in komodod's script interpreter. |
| Atomic swaps (With other chains) | ✓ | Script can express HTLCs, used by the Komodo DeFi Framework (AtomicDEX) swaps. |
| Native DEX (Trades the coin itself, not a claim) | ✓ | Traded as itself, not as a wrapped token or a claim: Komodo DeFi. |
| Cross-chain messaging (Verified by the chain itself) | ✗ | dPoW notarises KMD block hashes to Bitcoin, which is security anchoring, not messaging verified by the other chain's nodes. |
| NFTs (Carried by the chain's rules) | ✗ | No token or NFT type on the KMD chain itself. |
| Demand | 0.6 | average of 5 measures |
| Exchanges (10 or more: 10) | 0 | no exchange the site reads trades it |
| Daily volume ($10K 0, $1B or more 10) | 0 | $0 traded in 24 hours; #4358 by volume |
| Turnover (volume ÷ market cap, 5% a day: 10) | 0 | 0.00% of its market cap a day |
| Order-book depth (±2% of the price ÷ market cap, 1%: 10) | – | no order book on the nine exchanges read |
| Market cap ($1M 0, $10B or more 10) | 2 | $6.6M, 2 on a scale of 2.5 points per tenfold |
| Paper trading (futures, options and margin ÷ market cap, 0%: 10, 100%: 0) | – | not measured |
| Wallet support (wallets that hold it, 10 or more: 10) | 1 | its own node and wallet, counted as 1: no wallet in the site's directory lists it yet |
| Record | 8.3 | average of 3 criteria |
| Age (years since genesis) (Source) | 9 | 9 full years since 2017-02-05, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 6 | 2 positive, 1 negative source |
| Positive | ||
| Steady work, 6 of 6 | ✓ | 55 commits in 8 of the last 12 months (github.com/KomodoPlatform/komodo); Komodo 0.9.2-3, 18 Oct 2026; also 0.9.2-2 (Jun 2026), 0.9.2-1 (Jan 2026) and 0.9.2 (Dec 2025) in the last 24 months. |
| Shipped a security fix in two years, +1 | ✓ | Komodo 0.9.2-2, Jun 2026: fixed remotely reachable memory-safety bugs in block and script validation; 0.9.2-3, Oct 2026: CLTV script-parsing fix. |
| Negative | ||
| Unfixed vulnerability, disclosed 2024-07-03, −1 | ✗ | CVE-2020-14198: misbehaving peers are auto-banned into an unbounded ban list, so many attacker addresses can exhaust CPU and memory; still in Komodo v0.9.2-3. bitcoincore.org github.com github.com |
| Conduct (origin, claims, halts) | 10 | 3 positive, 0 negative source |
| Positive record | ||
| Launched with a stated purpose, not as a joke | ✓ | |
| No claims by its founders that contradict its own design | ✓ | |
| No halt, freeze or reversal in five years | ✓ | |
Ten sections, weighted equally, each 0 to 10: consensus (the two ladders), supply (the supply scale and a fixed cap that holds), distribution (premine, fundraising, developer share, holders), decentralisation (governance, no central team, who can mint, nodes), security, scalability, privacy, programmability (what the scripting layer can do beyond the whitepaper's payment system), demand, and record (age, development, conduct). They are built from the criteria in the second table: privacy, scalability, security and decentralisation are the Cryptocurrency Standards among them, as follows: privacy (the whitepaper's three checks a base of 7 of 10, three extra features up to 3 more), scalability (four measures and three features), security (pool diversity, network activity, hashrate, clients and two checks) and decentralisation (governance, no central team, who can mint, nodes, holders, premine, fundraising and developer share); programmability (token issuance, smart contracts and five checks) follows them, and supply and demand are two: the supply, scored against 21 million, and demand, the average of seven measures of the market and the wallets. Provisional: parts marked — are not yet measured and are left out of the average. A rating of structure and market depth, not a price forecast or investment advice. How the grade is built · Highest-graded cryptocurrencies.
135,953,876 KMD are in circulation, against no fixed cap — issuance has no defined end.
| Premine (allocated at launch) | 71.1% of today's supply |
|---|---|
| Sold by the issuer or insiders | 64% of today's supply |
| Developer share received since launch | 0% of today's supply |
| Developer share of new coins today | 0% |
| Fundraising | Public sale |
All 100M KMD at genesis were pre-allocated: 90M sold in the 2016 ICO and 10M kept by the team. Against current supply of 140,660,565 (CoinGecko, 2026-10-23) that is 71.1%.
Public ICO from 15 Oct to 20 Nov 2016 raised 2,639 BTC (about $2M), with a 25% first-day bonus; coins were issued 31 Jan 2017. 90M KMD sold.
The block reward (3 KMD, cut to 1 KMD by KIP0002 in 2024) goes to miners, including notary nodes. The active-user reward paid to holders (5%, cut to 0.01% by KIP0001 in 2023) is not a cut, and there is no dev fund in issuance.
The 90M/10M split comes from secondary sources (Bankbazaar and others); Coinstats claims 100M were distributed in the ICO. The supply base is disputed: CMC shows 135.95M, which would give 73.6% premine and 66.2% sold.
Sources: komodoplatform.com · komodoplatform.com · komodoplatform.com · komodoplatform.com · bitcoinist.com · komodoplatform.com. Researched 2026-10-24, medium confidence.
Komodo is secured by 697 kH/s of its own work. Hashrate does not compare across algorithms — a SHA-256 hash and a Scrypt hash cost different amounts to produce.
No SEC/CFTC determination — unclassified.
The regulator's position, reported as stated, not CoinSpectrum's. Assets nobody has ruled on are left unclassified rather than sorted by a guess.
Komodo is #154 among cryptocurrencies and #1078 in the market ranking, which lists wrapped coins, staked derivatives, stablecoins and tokens alongside them. CoinSpectrum counts an asset once, and counts only cryptocurrencies: assets with their own blockchain and their own consensus. A wrapped coin, a staked derivative or a stablecoin is a claim on something already counted; a token, memecoin or otherwise, runs on another chain's blocks. All of them are listed, each in its own section, and none is added to the total. The 924 places between Komodo's two ranks are held by claims and tokens, not by other networks. The methodology sets out the rule and the counting rule argues for it.
The price above is the median of the exchanges the site reads live, checked every minute and cross-checked against a market snapshot (how market data is gathered). The grade is scored on published criteria, each with its source (the method). The site is independent, nothing on it is a paid placement, and its statements are signed (about CoinSpectrum, the manifesto).