Obyte ranks #175 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #1262: 1087 of the 1261 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 1513 non-native assets CoinSpectrum lists above it by market cap, about 61% are tokens, 32% are claims on other assets, 7% are memecoins and 1% are NFT collections.
| CoinSpectrum Grade | A · 64/100 · provisional, B to A |
|---|---|
| Rank among cryptocurrencies | #175 |
| Rank counting claims | #1262 |
| Market capitalisation | $4M |
| Price | $4.31 |
| Circulating supply | 948,246 GBYTE |
| Maximum supply | 1,000,000 GBYTE |
| Consensus family | Federated |
| Consensus mechanism | Order-provider DAG (Byteball) |
| Ledger type | Multi-asset ledger |
| Launch distribution | Premine |
Market figures from the 10 November 2026 build. Open the live view for every exchange's price, and charts.
A — 64 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 65 (B to A).
| Section and criteria | Score | Basis |
|---|---|---|
| Consensus | 8.2 | average of 2 criteria |
| By leader (its largest chain's market cap) (Source) | 8.2 | Federated: 8.2 of 10 on the ladder of consensus families ranked by their largest chain's market cap |
| By family (all its chains' market cap) (Source) | 8.2 | Federated: 8.2 of 10 on the ladder of families ranked by the combined market cap of their chains |
| Supply | 7.7 | the supply scale times 0.9, and a point for a fixed cap that holds |
| Supply (21 million scores 10) | 7.4 | fixed maximum supply of 1 million |
| Distribution | 6.7 | average of 3 parts |
| Holder concentration (Source) | – | Not yet measured |
| Active addresses | – | Not yet measured |
| Premine (allocated at launch) | 0 | 100% of today's supply allocated at launch to founders, a company, a foundation or investors. The entire 10^15 bytes (1,000,000 GBYTE) were created in the genesis unit (Dec 2016); there is no mining or staking issuance. Distribution was by founder-designed airdrops (to BTC and byte holders, 645,341+ GBYTE through 2017), then cashback, referral and grant programmes. The founder and team kept ~1%. A chain with no open minting is 100. source |
| Fundraising (share sold) (Source) | 10 | No sale of the coin source |
| Developer share (after launch) | 10 | No developer share: every new coin goes to the miners or validators who produce blocks. The whole supply was created in the Dec 2016 genesis unit; there is no mining or staking issuance. source |
| Decentralisation | 3.9 | average of 4 parts |
| Governance (Source) | 10 | No authority can halt the chain or freeze funds: No protocol-level freeze, blacklist or clawback of bytes; order providers only order units and cannot block transfers, though the founder runs 5 of the 12 order-provider seats (7 are needed to advance the main chain). source |
| No central team (Source) | 0 | A central team directs it: The only node implementation, byteball/ocore (MIT) with its wallets, is developed by founder Tony (Anton) Churyumoff and the Obyte team / Obyte Foundation (Liechtenstein). source |
| Who can mint (Source) | 2 | Gated by registration: producers admitted by name, licence or company registration: an allow list, federation, council or proof of authority |
| Nodes (Source) | 3.5 | 11 active validators or block producers (source: Order) |
| Security | 4.7 | 3.8 of 8 points source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | 5.3 | largest 41.7%, largest three 58.3% |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | 0 | about 129 transactions a day |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | 1 | not mined: another consensus, 1 |
| 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) | 6 | one client, latest version Jan 2025, within 24 months |
| Open source (Node software) | ✓ | |
| No 51% attack (Nor a deep reorganisation, five years) | ✓ | |
| Scalability | 6.2 | average of 3 parts source |
| Fees ($0.001 or less 10, $1 or more 0) | 10 | typical fee $0.000005 |
| Throughput (2,478 a second, the busiest network's peak day, 10; 121, the median of the ten busiest, 5) | – | not yet measured |
| Block time (10 minutes 10, less either side) | 5.3 | a block every 30 seconds |
| Block space per 10 minutes (24 MB or more 10: the ten busiest networks' median demand, 16.4 MB, and half again for growth) | – | not yet measured |
| Features (3 checks) | 3.3 | 1 of 3 passed |
| Fast payments (Safe to accept within seconds · Whitepaper abstract, §1, §2 and §11) | ✗ | A unit becomes final when it is stabilised by the order providers' units on the main chain, which takes minutes, and there is no protected zero-confirmation mechanism. |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | ✗ | Full nodes keep the whole DAG; no pruning mode. |
| Light clients (Payments verified from headers · Whitepaper §8) | ✓ | ocore light clients receive witness proofs and a proofchain from a light vendor and verify them against order-provider signatures (light.js / witness_proof.js). |
| Privacy | 7 | 7 of 10: whitepaper privacy 7 of 7, extra features 0 of 3, 1 not yet researched source |
| Protocol level privacy (Keys not tied to an identity · Whitepaper §10) | 10 | Accounts are created from keys users generate themselves; transfers are validated by signature, with no identity condition in the protocol. |
| 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) | 0 | Private payments apply only to separate private assets such as blackbytes; native GBYTE transfers show their amounts. |
| Hidden parties (Sender and receiver hidden) | 0 | No ring signatures, ZK sender proofs or stealth addresses; private payments rely on off-chain payload transfer instead. |
| Network privacy (Origin hidden by default) | 0 | Units are broadcast directly to hubs and peers over WebSocket; no Dandelion or built-in Tor by default. |
| Programmability | 8.9 | 8 of 9 points source |
| Token issuance (At protocol level) | 2 | Native assets that any address can define and issue, plus Autonomous Agents (Oscript contracts) that can issue assets. |
| Smart contracts (General-purpose) | 2 | Autonomous Agents written in Oscript, deployable from public editors, run DEXs (Oswap), stablecoins and other applications on mainnet. |
| Multisig and time locks (Without a third party) | ✓ | Address definitions support 'r of set' (m-of-n signatures) and 'timestamp'/'mci' conditions in the ocore validation rules. |
| Atomic swaps (With other chains) | ✓ | Address definitions combine 'hash' (preimage reveal) with time conditions, which expresses an HTLC. |
| Native DEX (Trades the coin itself, not a claim) | ✓ | Traded as itself, not as a wrapped token or a claim: its own chain's DEXes (Obyte, DefiLlama). |
| Cross-chain messaging (Verified by the chain itself) | ✗ | Counterstake bridges are Autonomous Agents secured by stakers' claims and challenges, not cross-chain verification by Obyte nodes. |
| NFTs (Carried by the chain's rules) | ✓ | Native assets any address can define, with a cap (total supply) that can be set to 1 for a unique token. |
| Demand | 2.3 | average of 6 measures |
| Exchanges (10 or more: 10) | 1 | 1 exchange |
| Daily volume ($10K 0, $1B or more 10) | 0 | $6 traded in 24 hours; #4234 by volume on the exchanges the site reads (scored on the median day of the last 30, $12) |
| Turnover (volume ÷ market cap, 5% a day: 10) | 0 | 0.00% of its market cap a day, median of the last 30 days |
| 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) | 1.5 | $4.1M, 1.5 on a scale of 2.5 points per tenfold |
| Paper trading (futures, options and margin ÷ market cap, 0%: 10, 100%: 0) | 10 | no futures, options or margin on the exchanges read |
| 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.5 | average of 3 criteria |
| Age (years since genesis) (Source) | 9 | 9 full years since 2016-12-27, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 6.5 | 2 positive, 0 negative source |
| Positive | ||
| Steady work, 5.5 of 6 | ✓ | 77 commits in 11 of the last 12 months (github.com/byteball/obyte-gui-wallet); By the release rule: the reference wallet/full node byteball/obyte-gui-wallet shipped v5.0.1 (2024-12-05) and v5.0.2 (2025-01-21) in the last 24 months, after v5.0.0 on 2024-10-25; the core library byteball/ocore (MIT, untagged) is still committed to (last 2026-10-22, with an upcoming protocol upgrade being postponed), so development is ongoing even though releases are sparse. |
| Shipped a new capability for users in two years, +1 | ✓ | Obyte v4 network upgrade (wallet 5.0.0, activated at MCI 10968000, Nov 2024): temporary data posting and on-chain voting for order providers and system variables. |
| 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.
948,246 of a maximum 1,000,000 GBYTE are in circulation — 94.8% of the total that will ever exist.
| Premine (allocated at launch) | 100% of today's supply |
|---|---|
| Sold by the issuer or insiders | 0% of today's supply |
| Developer share received since launch | 0% of today's supply |
| Developer share of new coins today | 0% |
| Nodes or validators | 11 |
| Fundraising | No sale and no investor round |
The entire 10^15 bytes (1,000,000 GBYTE) were created in the genesis unit (Dec 2016); there is no mining or staking issuance. Distribution was by founder-designed airdrops (to BTC and byte holders, 645,341+ GBYTE through 2017), then cashback, referral and grant programmes. The founder and team kept ~1%. A chain with no open minting is 100.
No ICO or sale; free distribution. About 85% of supply reportedly distributed via programmes, grants and rewards. Any market sales from the undistributed funds are not documented.
The whole supply was created in the Dec 2016 genesis unit; there is no mining or staking issuance.
Founder-retained share is given as 1% (99% distributed) in secondary sources; one query premise of 98% isn't supported. The 100 reflects the brief's rule (no open minting, founder-decided airdrops), not a large team holding.
Sources: obyte.org · hackernoon.com · sia.hackernoon.com · coinranking.com · btc-echo.de. Researched 2026-10-26, high confidence.
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.
Obyte is #175 among cryptocurrencies and #1262 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 1087 places between Obyte'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).