Layer-1 application blockchain · since 2014
Thousands of chains have launched and gone quiet since 2014. I/O Coin has produced blocks without a single halt — no premine, no ICO, no relaunch. The swap to Proof-of-Stake was written into the consensus code before launch and executed live around block 24,400. Every block is still verifiable, by anyone, today.
Genesis · 24 July 2014
Everything below can be checked. The source is public, the chain is public, and where a number isn't published anywhere, this page says so instead of inventing one.
No premine. No ICO. No founder allocation. The two-week mining period ran on PoW-X11, chosen because it was video-card resistant — that made insta-mining very hard, so no one could sit on a farm and take the supply before anyone else showed up.
That number was in the launch rules, not a decision made later. The chain hit it around height 24,400 and every node has rejected mined blocks since. No fork. No relaunch.
Blocks since July 2014, without a break. We don't say "100% uptime" because that's a marketing number. The chain has never halted. Check an explorer.
Every one of those coins was mined in the open during a two-week PoW-X11 mining period. At block 24,400 it stopped and stake took over. Both figures come from the public chain, so neither has to be taken on trust.
This is DIONS. Most chains move coins and leave names, messaging and storage to whatever gets built on top later — these went into the protocol itself, in 2014. The full system launched in 2017 and has run on mainnet from then to today. DIONS 2.0 is the upgrade to it: the same chain, rewritten underneath.
An alias is an account with a readable name, resolved on the chain. No registrar, no renewal invoice, no company that can take it back.
Direct messages and channels, encrypted under AES-256 before they are published. Holding the key is the only way in.
Files and payloads ride with the record. The content stays private; the hash is public, so anyone can verify a claim without reading what it refers to.
Stake and produce blocks, or relay and earn from a zero balance with headers only. There is no minimum stake in consensus — small stakes just win less often.
A full rewrite of the node in C++20. Stake still produces the blocks. Everything new sits behind an activation gate, which means it switches on at a set block height rather than shipping live on day one.
Status labels mirror the source: In code is implemented, Testnet runs on the public testnet, Not claimed is a target or dormant. Mainnet has not launched.
Most enterprise data sits on a server somebody owns. If that vendor folds, loses the contract or gets bought, the record goes with it. A chain that carries the data itself removes that dependency — and this one has been carrying it since 2017.
Record privacy was designed against HIPAA obligations for data at rest and in transit, not against anyone looking for anonymous money. The design target was compliance.
The hash is public and timestamped by the chain; the contents stay encrypted. An auditor can confirm a record existed and has not changed without ever reading it.
Aliases bind keys to readable names today. In DIONS 2.0 the same records bind to autonomous agents and hardware through W3C DID-direction records.
AES-256 before anything is published, with direct messages, channels and file transfer up to 1 MB a record. Nothing routes through a mail host you have to trust.
The node is open source and the chain is public. Running it costs what the hardware costs. There is nothing to renew annually and nobody who can switch you off.
Blocks since July 2014 with no halt, no relaunch and no chain reset. For a record that has to still be checkable in a decade, continuity is the product.
Everything above runs on mainnet today under DIONS. DIONS 2.0 is on public testnet and has not launched on mainnet — where this page describes a 2.0 capability, it says so. Talk to the Foundation at iodigital.io.
Sixteen moments where a real choice carried a real cost. Taken together they are the reason the chain is still producing blocks on its original ledger.
Twelve days after genesis the team published three goals. Most projects quietly drop the early roadmap; all three of these shipped. The harder proof came after: that a chain could carry the data itself, instead of pointing at a server holding it for you.
A full HTML5 wallet with interchangeable skins — a first for a Proof-of-Stake coin.
Readable aliases instead of address strings, shipped inside the wallet as IONS.
Blocks without a halt ever since, and the chains that followed took the same route.
The record written into the ledger, not a hash pointing at somebody’s server.
Messages, channels and file transfer, AES-256 before anything is published.
Up to 1 MB each: content stays private, the hash stays public, the claim stays checkable.
Stealth addressing aimed at HIPAA data obligations, not at anonymous money.
gettxout gave decentralised exchanges what they need to settle against the chain.
Aliases binding keys to names, agents and hardware through W3C DID-direction records.
The Foundation was set up in 2016 to curate the codebase, work with partners and run community initiatives — including charity work such as mangrove preservation in Indonesia. The project was recognised that year by Benzinga, the European Fintech 100 and the KPMG Fintech 100. The codebase it curates is public, and every line can be read.
Three initiatives remain unfinished and the Foundation says so plainly: the DVM, Nighthawk — around 90% complete, deliberately held so DIONS 2.0 ships first — and Chameleon, announced at the North American Bitcoin Conference in January 2019.
Engineering archive →Both are full nodes and both stake. The difference is how much of the chain you want to deal with.
0.1.1-RC10 · 22 June 2026
Installs iocoind and runs it for you in the background. You get balance,
send and receive, staking and an address book — and legacy sync is far quicker than the
old client. The RPC port stays on localhost, so nothing is reachable from outside.
The original desktop wallet
The complete client, with the DIONS surface the Widget Wallet does not expose: aliases, encrypted messaging, data records and file transfer. Heavier, and a first sync takes longer unless you use the bootstrap package.
Ten years of development notes, community letters and post-mortems — published at the time, not reconstructed later. They are the source for most of this page.