DigiByte ranks #74 of 508 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #386: 312 of the 385 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 395 non-native assets CoinSpectrum lists above it by market cap, about 53% are tokens, 39% are claims on other assets and 7% are memecoins.
| CoinSpectrum Grade | A+ · 83/100 · provisional |
|---|---|
| Rank among cryptocurrencies | #74 |
| Rank counting claims | #386 |
| Market capitalisation | $63M |
| Price | $0.00340 |
| Circulating supply | 18,535,061,210 DGB |
| Maximum supply | 21,000,000,000 DGB |
| Consensus family | Proof of Work |
| Consensus mechanism | MultiAlgo (5 PoW algos: SHA256/Scrypt/Skein/Qubit/Odocrypt) |
| Own hashrate | 59 PH/s |
| Network purpose | Payments |
| Ledger type | Overlay-asset ledger |
| Launch distribution | No premine |
Market figures from the 28 October 2026 build. Open the live view for every exchange's price, and charts.
A+ — 83 out of 100, provisional (from 16 of 17 criteria, 28 October 2026 build). With what is not yet measured anywhere from nothing to full marks, the score would be 78 to 85 (A to A+).
| Criterion | Score | Basis |
|---|---|---|
| Leading Consensus Mechanisms (Source) | 10 | group average |
| Consensus: leader ladder | 10 | Proof of work: 10 of 10 on the ladder of consensus families ranked by their largest chain's market cap |
| Consensus: family ladder | 10 | Proof of work: 10 of 10 on the ladder of families ranked by the combined market cap of their chains |
| Cryptocurrency Standards | 8.1 | group average, 5 of 6 measured |
| Properties (10 whitepaper checks) (Source) | 8 | 8 of 10 passed source |
| Anyone can mint (permissionless) | ✓ | MultiAlgo (5 PoW algos: SHA256/Scrypt/Skein/Qubit/Odocrypt) |
| Limited supply | ✓ | fixed maximum of 21,000,000,000 |
| No pre-issuance or developer mint | ✓ | |
| No developer tax | ✓ | |
| No authority that can halt the chain or freeze funds | ✓ | No protocol-level party can freeze coins or halt the chain. |
| No central team | ✓ | DigiByte Core is maintained by volunteer developers in the DigiByte-Core repository, with no controlling company. |
| Fees under one cent | ✓ | typical fee $0.000047 |
| Payments safe to accept within seconds | ✗ | 15-second probabilistic multi-algorithm blocks; no double-spend proofs or instant locks protect zero-confirmation payments. |
| UTXO ledger | ✓ | |
| Privacy built into the protocol | ✗ | |
| Scalability (fees, throughput, block time, block space) | 8.3 | average of 4 measures source |
| Fees ($0.001 or less 10, $1 or more 0) | 10 | typical fee $0.000047 |
| Throughput (1,000 transactions a second or more 10) | 8.9 | about 473 simple transactions a second |
| Block time (10 minutes 10, less either side) | 4.2 | a block every 15 seconds |
| Block space per 10 minutes (32 MB or more 10) | 10 | 4 MB limit, 160 MB per 10 minutes |
| Security (9 checks) | 5.1 | 4 of 9 passed, 2 not yet measured source |
| Miners paid over $1 million a day | ✗ | about $4,855 a day |
| Miners paid over $100,000 a day | ✗ | |
| Its own hashrate: at least half its algorithm's largest, not merge-mined | ✓ | |
| Largest pool or validator under 50% | – | |
| Largest three under 75% | – | |
| More than one maintained client | ✗ | 1 |
| Node software is open source | ✓ | DigiByte Core is maintained by volunteer developers in the DigiByte-Core repository, with no controlling company. |
| Real on-chain use: 1,000+ transactions a day | ✓ | about 1,905 a day |
| No 51% attack or deep reorganisation in five years | ✓ | |
| Decentralisation: who can mint (Source) | 10 | Proof of work: 10 of 10 on the ladder of who produces blocks |
| Decentralisation: nodes (Source) | 9.3 | 635 reachable nodes (source: digibyte.io) |
| Decentralisation: holder concentration (Source) | — | Not yet measured |
| Capabilities (protocol features) | 5 | 3 of 6 passed source |
| Decentralisation | ||
| Network-level privacy: the node hides where a transaction came from (Dandelion++, Tor or I2P, on by default) | ✓ | DigiByte Core relays transactions by Dandelion++ by default (-dandelion, DEFAULT_DANDELION = true, since 7.17; still on in v9.26.7, Oct 2026). |
| Light clients verify payments from headers or proofs, without a trusted server | ✓ | Bitcoin-style SPV with headers and Merkle proofs. |
| Scalability | ||
| Pruned nodes: a full node can validate and drop old history | ✓ | DigiByte Core -prune deletes old blocks. |
| Native payment channels or instant payments | ✗ | No live payment-channel network. |
| Security | ||
| Hidden amounts (confidential transactions, RingCT, shielded pools, Mimblewimble) | ✗ | No confidential transactions. |
| Hidden sender and receiver (ring signatures or zero-knowledge proofs, one-time or stealth addresses) | ✗ | Dandelion++ hides the origin IP only; no ring signatures or stealth addresses. |
| Issuance | 10 | group average |
| Premine (allocated at launch) | 10 | Fair launch: no premine |
| Fundraising | 10 | No sale of the coin |
| Developer share (after launch) | 10 | No developer share: every new coin goes to the miners who produce blocks |
| Supply & Demand | 4.9 | group average |
| Supply & Demand (Source) | 6.1 | average of 6 measures |
| Exchanges (10 or more: 10) | 10 | 21 exchanges |
| Volume rank among the top 200 | 0 | $158,373 traded in 24 hours; #677 by volume on the exchanges the site reads (ranked on the median day of the last 30, $926,428) |
| Turnover (volume ÷ market cap, 5% a day: 10) | 7 | 1.4% of its market cap a day, median of the last 30 days |
| Order-book depth (bids and asks within 2% ÷ market cap, 1%: 10) | 5 | $20,288 within 2% of the price on 4 exchanges, 0.03% of its market cap, median of the last 2 days |
| Market cap ($1M 0, $10B or more 10) | 4.5 | $63M, 4.5 on a scale of 2.5 points per tenfold |
| Futures exposure (open interest ÷ market cap, less is better) | 10 | no perpetual futures on the exchanges read |
| Supply (smaller is better) | 3.6 | fixed maximum supply of 21 billion |
| Record | 9.3 | group average |
| Record (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 | ✓ | |
| Age (years since genesis) (Source) | 10 | 12 full years since 2014-02-06, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, improvements, unfixed issues) | 8 | 4 positive, 1 negative, 1 not yet researched source |
| Positive | ||
| Steady work, 6 of 6 | ✓ | 1,591 commits in 11 of the last 12 months (github.com/DigiByte-Core/digibyte); DigiByte Core v9.26.7, released 2026-10-06. |
| Shipped a security fix in two years, +1 | ✓ | DigiByte v9.26.2, 30 Jun 2026: fixed the retired-algorithm (Groestl) block acceptance exploit. |
| Shipped a new capability for users in two years, +1 | ✓ | DigiDollar activated on mainnet at block 23,869,440, 17 Jul 2026 (v9.26.2-v9.26.5). |
| Token issuance through a metaprotocol, +1 | ✓ | DigiAssets: read by indexers, not validated by the chain's nodes |
| Negative | ||
| Unfixed vulnerability, disclosed 2026-05-05, −1 | ✗ | CVE-2024-52911: a crafted invalid block can make script-check threads read freed precomputed transaction data and crash the node; still in DigiByte v9.26.7. |
| Not yet researched | ||
| Shipped a scaling upgrade in two years | – | |
Seventeen criteria, weighted equally. The Cryptocurrency Standards group four parts: properties (ten checks drawn from the Bitcoin whitepaper), scalability (four measures), security (nine checks) and decentralisation (three scales). Provisional: criteria 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.
18,535,061,210 of a maximum 21,000,000,000 DGB are in circulation — 88.3% of the total that will ever exist.
| Nodes or validators | 635 |
|---|
DigiByte is secured by 59 PH/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.
DigiByte is #74 among cryptocurrencies and #386 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 312 places between DigiByte'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).