Radiant (RXD)
Radiant ranks #253 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #2241: 1988 of the 2240 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 2535 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+ · 76/100 · provisional, A to A+ |
|---|---|
| Rank among cryptocurrencies | #253 |
| Rank counting claims | #2241 |
| Market capitalisation | $499,923 |
| Price | $0.0000314 |
| Circulating supply | 15,900,130,388 RXD |
| Maximum supply | 21,000,000,000 RXD |
| Consensus family | Proof of Work |
| Consensus mechanism | SHA512/256d |
| Own hashrate | 151 TH/s |
| Network purpose | Smart-contract platform |
| 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+ — 76 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 66 to 78 (A 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 | 7.3 | the supply scale times 0.9, and a point for a fixed cap that holds |
| Supply (21 million scores 10) | 7 | fixed maximum supply of 21 billion |
| 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. Genesis 2022-06-20 ('The New York Times 12/May/2022 The Milky Way's Black Hole Comes to Light'); 50,000 RXD per block to miners from block 1 with no allocation, presale or dev fund. Supply 16.45B at height 476,077 matches the schedule exactly (210,000 x 50,000 + 210,000 x 25,000 + 56,077 x 12,500). 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. GetBlockSubsidy in Radiant Core pays 50,000 RXD halving every 210,000 blocks entirely to the miner; no developer or treasury output. source |
| Decentralisation | 8.7 | average of 4 parts |
| Governance (Source) | 10 | No authority can halt the chain or freeze funds: No protocol key can freeze coins or halt the chain; deep-reorg finalization is a local node policy, not a party's power. source |
| No central team (Source) | 10 | No central team: Radiant Core (MIT) describes itself as a community-driven free software project in the Radiant-Core GitHub organisation; the original anonymous RadiantBlockchain developers no longer release, and no company or foundation controls the client. source |
| Who can mint (Source) | 10 | Open to anyone with hardware: anyone can produce blocks by mining, no permission needed |
| Nodes (Source) | 4.9 | 30 reachable nodes (distinct IP addresses at the chain's tip, crawled by CoinSpectrum on 2026-11-08; clearnet only) |
| Security | 5.9 | 2.4 of 4 points, 4 not yet measured source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | – | |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | – | |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | 6.5 | own work 5; about 115 kW, 1.5 of 5; the largest on its algorithm |
| 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 Jun 2026 |
| Open source (Node software) | ✓ | |
| No 51% attack (Nor a deep reorganisation, five years) | ✗ | 2026-06-15: Orphan race deeper than 6 blocks from fork base 438,203 (races of 13-28 blocks observed); v3.x nodes auto-finalized the minority branch at depth 6 and banned peers announcing the heavier chain, splitting the network until Radiant Core 3.1.2 added a checkpoint at 438,204. |
| Scalability | 9.8 | average of 5 parts source |
| Fees ($0.001 or less 10, $1 or more 0) | 10 | typical fee $0.000001 |
| Throughput (2,478 a second, the busiest network's peak day, 10; 121, the median of the ten busiest, 5) | 10 | about 3,776 simple transactions a second |
| 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) | 10 | 256 MB limit, 512 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) | ✓ | Bitcoin Cash Node-derived: first-seen mempool with no replace-by-fee, and Radiant Core relays double-spend proofs (DSProof), so zero-confirmation payments are network-protected. |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | ✓ | -prune inherited from the Bitcoin/BCHN codebase. |
| Light clients (Payments verified from headers · Whitepaper §8) | ✓ | BCHN-derived SHA512/256d PoW header chain with merkleblock Merkle proofs (SPV). |
| 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 | 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) | 0 | Transparent transactions: amounts are public on chain. |
| Hidden parties (Sender and receiver hidden) | 0 | Transparent addresses: sender and receiver are public on chain. |
| Network privacy (Origin hidden by default) | 0 | No Dandelion relay; Tor/onion is an optional -onion/-proxy setting in the Bitcoin-derived node, not on by default. |
| Programmability | 7.8 | 7 of 9 points source |
| Token issuance (At protocol level) | 2 | Glyph tokens built on Radiant's consensus-level references (refs) and induction-proof scripts, so token supply rules are enforced by miners, not indexers; anyone can mint. |
| Smart contracts (General-purpose) | 2 | Radiant Script with references, induction proofs and introspection opcodes (OP_REQUIREINPUTREF, OP_CODESCRIPTHASHVALUESUM_UTXOS), on which Glyph tokens and decentralised mint contracts run on layer one. |
| Multisig and time locks (Without a third party) | ✓ | CHECKMULTISIG plus CLTV and CSV (activation heights 100 and 102) in radiant-node mainnet parameters. |
| Atomic swaps (With other chains) | ✓ | HTLCs expressible with OP_SHA256/OP_HASH160 and OP_CHECKLOCKTIMEVERIFY. |
| Native DEX (Trades the coin itself, not a claim) | ✗ | No DEX found trading the coin itself: none on its own chain (DefiLlama), and not on THORChain, Maya, Chainflip, Komodo DeFi, BasicSwap, Bisq or Haveno (checked 2026-11-04). |
| Cross-chain messaging (Verified by the chain itself) | ✗ | No protocol-level cross-chain messaging. |
| NFTs (Carried by the chain's rules) | ✓ | Glyph NFTs on singleton refs; the consensus rules allow only one instance of a singleton ref. |
| 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,174 traded in 24 hours; #3027 by volume on the exchanges the site reads (scored on the median day of the last 15, $2,555) |
| Turnover (volume ÷ market cap, 5% a day: 10) | 5 | 0.57% of its market cap a day, median of the last 16 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 | $500K, 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.3 | average of 3 criteria |
| Age (years since genesis) (Source) | 3 | 3 full years since 2022-12-05, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 6 | 3 positive, 2 negative source |
| Positive | ||
| Steady work, 6 of 6 | ✓ | 268 commits in 8 of the last 12 months (github.com/Radiant-Core/Radiant-Core); Radiant Core v3.1.2 released 2026-06-16 (v2.0.1 Feb 2026 through v3.1.2: ten releases in 2026); the original RadiantBlockchain/radiant-node stopped at v1.3.0 (2024-04). |
| Shipped a security fix in two years, +1 | ✓ | Radiant Core v2.1.0, Feb 2026: fixed a critical BLAKE3 crash on oversized input and bounded shift amounts; v3.1.0/3.1.1 (Jun 2026) remediated an audit's 5 critical and 18 high findings with the SCRIPT_SECURITY_UPGRADE at block 440,000. |
| Shipped a new capability for users in two years, +1 | ✓ | Radiant Core v2.0.1/v2.1.0 hard fork at block 410,000 (Feb-Mar 2026): new OP_BLAKE3 and OP_K12 opcodes, and OP_LSHIFT, OP_RSHIFT, OP_2MUL and OP_2DIV re-enabled. |
| Negative | ||
| Unfixed vulnerability, disclosed 2024-07-03, −1 | ✗ | CVE-2024-52914: crafted orphan transactions can stall the node in the uninterruptible orphan-resolution loop, limited only by a cap of five rejected orphans per peer; still in Radiant v3.1.2. bitcoincore.org github.com github.com |
| Unfixed vulnerability, disclosed 2024-10-08, −1 | ✗ | CVE-2024-35202: a crafted blocktxn message trips the assert in compact-block reconstruction and crashes the node; still in Radiant v3.1.2. 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.
Proof of Work coins
Bitcoin BTCA+
Zcash ZECA+
Dogecoin DOGEA+
Luckycoin LKYA
Garlicoin GRLC
Neurai XNAA
Hacash Diamond HACDAAll 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
15,900,130,388 of a maximum 21,000,000,000 RXD are in circulation — 75.7% 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 |
Genesis 2022-06-20 ('The New York Times 12/May/2022 The Milky Way's Black Hole Comes to Light'); 50,000 RXD per block to miners from block 1 with no allocation, presale or dev fund. Supply 16.45B at height 476,077 matches the schedule exactly (210,000 x 50,000 + 210,000 x 25,000 + 56,077 x 12,500).
Fair launch by anonymous developers in June 2022; no ICO or presale.
No sale or investor round.
GetBlockSubsidy in Radiant Core pays 50,000 RXD halving every 210,000 blocks entirely to the miner; no developer or treasury output.
The June 2026 split was a natural orphan race made persistent by node defaults, not a documented hostile attack; it is listed because it was a reorganisation deeper than six blocks. Radiant Core 3.1.2 raised the auto-finalization depth from 6 to 69 blocks.
Sources: github.com · raw.githubusercontent.com · raw.githubusercontent.com · github.com · radiantexplorer.com. Researched 2026-10-26, medium confidence.
The work behind it
Radiant is secured by 151 TH/s of its own work. Hashrate does not compare across algorithms — a SHA-256 hash and a Scrypt hash cost different amounts to produce.
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 Radiant
Radiant is #253 among cryptocurrencies and #2241 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 1988 places between Radiant'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).