Hacash Diamond (HACD)
Hacash Diamond ranks #255 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #1589: 1334 of the 1588 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 2576 non-native assets CoinSpectrum lists above it by market cap, about 61% are tokens, 34% are claims on other assets, 4% are memecoins and 1% are NFT collections.
| CoinSpectrum Grade | A · 66/100 · provisional, C to A+ |
|---|---|
| Rank among cryptocurrencies | #255 |
| Rank counting claims | #1589 |
| Market capitalisation | $460,447 |
| Price | $3.29 |
| Circulating supply | 139,789 HACD |
| Maximum supply | 16,777,216 HACD |
| Consensus family | Proof of Work |
| Consensus mechanism | X16RS |
| Own hashrate | — |
| Ledger type | Single-asset ledger |
| Launch distribution | No premine |
Market figures from the 10 November 2026 build. Open the live view for every exchange's price, and charts.
CoinSpectrum Grade (Source)
A — 66 out of 100, provisional (from 8 of 10 sections, 10 November 2026 build). With what is not yet measured anywhere from nothing to full marks, the score would be 46 to 75 (C 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 | 9.8 | fixed maximum supply of 16.8 million |
| Distribution | 10 | average of 3 parts |
| Holder concentration (Source) | – | Not yet measured |
| Active addresses | – | Not yet measured |
| Premine (allocated at launch) | 10 | 0% of today's supply allocated at launch to founders, a company, a foundation or investors. No premine and no team allocation. Every HACD is mined by PoW (one per qualifying 6-letter diamond, max 58/day) and must win a HAC bid, which burns HAC. Mining started 2019-05-16. 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. Each HACD is awarded to the miner who finds the qualifying diamond and wins its HAC bid, which burns HAC. No developer or treasury share of HACD exists. source |
| Decentralisation | 6.7 | average of 3 parts |
| Governance (Source) | 10 | No authority can halt the chain or freeze funds: No protocol-level party can freeze, blacklist or claw back HAC or HACD. source |
| No central team (Source) | 0 | A central team directs it: The reference node hacash/fullnode is developed by the Hacash core team under the hacash GitHub organisation; its repository carries no licence file (predecessor repos hacash/core, hacash/node and hacash/rust are MIT). 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 | 3.1 | 2.5 of 8 points source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | 0.3 | largest 66.2%, largest three 87.5% |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | 0.4 | about 333 transactions a day |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | 6.6 | own work 5; about 158 kW (estimated from its miner pay), 1.6 of 5 |
| 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 | — | too few measures yet source |
| Fees ($0.001 or less 10, $1 or more 0) | – | not yet measured |
| 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) | 8.9 | a block every 5 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) | – | not yet measured |
| Features (3 checks) | 0 | 0 of 1 passed, 2 not yet researched |
| Fast payments (Safe to accept within seconds · Whitepaper abstract, §1, §2 and §11) | ✗ | Five-minute PoW blocks with probabilistic confirmation; Hacash's payment channels are a layer-2 feature, not network-protected zero-conf. |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | – | No pruning option documented for hacash/fullnode. |
| Light clients (Payments verified from headers · Whitepaper §8) | – | No light-client protocol documented. |
| Privacy | 3.5 | 3.5 of 10: whitepaper privacy 3.5 of 7, extra features 0 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) | 0 | An account ledger: one running balance for each address, so the remainder stays at the sending address and its payments share one public history. |
| HD addresses (A new address for each payment, unlinked · Whitepaper §10) | – | |
| Hidden amounts (Amounts confidential) | 0 | Balances and transfers are public. |
| Hidden parties (Sender and receiver hidden) | 0 | Sender and receiver addresses are public. |
| Network privacy (Origin hidden by default) | 0 | Hacash fullnode relays transactions directly; no Dandelion or Tor. |
| Programmability | — | 3 of 4 points, 5 not yet researched |
| Token issuance (At protocol level) | 2 | AssetCreate action in Hacash's consensus rules, live on mainnet since block 765,432 (mid-2026), lets any address issue a fungible asset for a burned HAC fee; HACD diamonds themselves are protocol-minted. |
| Smart contracts | – | The Rust fullnode ships a contract VM with mainnet gas and storage parameters, but no fetched source establishes when contract deployment opened on mainnet or what runs there. |
| Multisig and time locks (Without a third party) | – | Not established: type-3 transactions allow up to 200 signers and channels carry an arbitration lock, but no source confirms m-of-n spending conditions with time locks. |
| Atomic swaps (With other chains) | – | Not established: no HTLC action found in the node's mint-core actions; VM capabilities unconfirmed. |
| Native DEX (Trades the coin itself, not a claim) | – | Not established: mainnet parameters name 'tex' diamond-trade limits, but no source describes them as an exchange. |
| Cross-chain messaging (Verified by the chain itself) | ✗ | No cross-chain messaging verified by Hacash nodes found in the fullnode. |
| NFTs (Carried by the chain's rules) | ✓ | HACD diamonds are unique, numbered non-fungible assets in Hacash's consensus rules, mined by anyone with PoW and transferred natively. |
| Demand | 2.8 | average of 6 measures |
| Exchanges (10 or more: 10) | 1 | 1 exchange |
| Daily volume ($10K 0, $1B or more 10) | 0 | $3,162 traded in 24 hours; #2990 by volume on the exchanges the site reads (scored on the median day of the last 9, $2,862) |
| Turnover (volume ÷ market cap, 5% a day: 10) | 4.7 | 0.51% of its market cap a day, median of the last 9 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) | 0 | $460K, 0 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 | 6.7 | average of 3 criteria |
| Age (years since genesis) (Source) | 2 | 2 full years since 2023-11-30, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 8 | 3 positive, 0 negative source |
| Positive | ||
| Steady work, 6 of 6 | ✓ | 145 commits in 8 of the last 12 months (github.com/hacash/fullnode); hacash/fullnode (Rust) v1.2.5 released 2026-10-18, with v1.2.1-v1.2.4 in Sept-Oct 2026. |
| Shipped a security fix in two years, +1 | ✓ | Hacash fullnode v1.0.4, Apr 2026: replaced LWMA difficulty with ASERT at height 738,654 to fix block-time oscillation (consensus fix). |
| Shipped a new capability for users in two years, +1 | ✓ | Hacash Istanbul upgrade (fullnode v1.0.9, Jul 2026) and v1.1.1–v1.2.4 (Sep–Oct 2026): HVM smart contracts, intents and new VM native functions. |
| 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.
Proof of Work coins
Bitcoin BTCA+
Zcash ZECA+
Dogecoin DOGEA+
Radiant RXDA+
Neurai XNAA
BitcoinZ BTCZA
CannabisCoin CANNAll Proof of Work chains →Proof of Stake coins
Ethereum ETHA+
BNB BNBA
Solana SOLA+
TRON TRXA
Hyperliquid HYPEB
Cardano ADAA
NEAR Protocol NEARAAll Proof of Stake chains →Supply
139,789 of a maximum 16,777,216 HACD are in circulation — 0.8% of the total that will ever exist.
Launch and allocation
| Premine (allocated at launch) | 0% 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% |
| Fundraising | No sale and no investor round |
No premine and no team allocation. Every HACD is mined by PoW (one per qualifying 6-letter diamond, max 58/day) and must win a HAC bid, which burns HAC. Mining started 2019-05-16.
No sale, no fundraising, no developer reward (project statements).
Each HACD is awarded to the miner who finds the qualifying diamond and wins its HAC bid, which burns HAC. No developer or treasury share of HACD exists.
The no-premine claim comes from the project and exchange explainers and is consistent with HACD being created only by mining plus a HAC burn.
Sources: hacash.org · github.com · coingecko.com · stakingrewards.com · coinex.com. Researched 2026-10-24, high confidence.
The work behind it
No source we can reach publishes a hashrate for Hacash Diamond.
What a regulator has said
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.
How CoinSpectrum ranks Hacash Diamond
Hacash Diamond is #255 among cryptocurrencies and #1589 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 1334 places between Hacash Diamond'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).