Proof of Stake when mining still owned the room
IOC moved beyond permanent mining escalation in its first weeks. That was not the easy market narrative in 2014.
proof-of-stake chain / encrypted records / dions protocol work
I/O Coin
Launched in 2014. Still running. Still pushing names, data, identity, messaging, privacy, and APIs beyond payment-only blockchains.
2014 genesis
no premine
proof of stake
dions testnet
ioc / genesis 2014-07-24 / fair launch / proof-of-stake chain
I/O Coin kept building the parts the market later learned it needed.
A short Proof-of-Work distribution. No premine. An early transition into Proof of Stake. Then years of work on human-readable names, encrypted data, messaging, identities, wallet applications, privacy direction, APIs, and DIONS.
01 / the record
The important claim is simple: IOC was early, and it stayed technical.
Fair-launch origin before the funding era changed incentives
No premine is not decoration. It explains why the project record matters differently than venture-backed or ICO-era chains.
Not only payments: names, data, messages, identity
The work moved toward user-held records: aliases, encrypted data payloads, messaging, files, proof of ownership, and APIs.
02 / what it was up against
The chain was building through several market headwinds at once.
The default belief was that serious security meant mining power. IOC had to prove stake-secured persistence while the market watched hash rate.
Names, messaging, files, and user profiles were being captured by platforms. IOC kept pushing toward key-held identity and encrypted records.
Later projects bought attention with treasury scale. IOC's record is built more like research continuity than a marketing cycle.
Crypto often forgets earlier engineering when newer platforms rename old ideas. This site is meant to restore the sequence.
03 / development record
A compressed history of the work.
Chain launch
I/O Coin launched with a short X11 Proof-of-Work distribution period and no premine.
Proof-of-Stake transition
The network moved into Proof of Stake around block 24400, establishing the chain's efficient-security direction early.
IONS and wallet usability
The mission pushed past raw addresses and Bitcoin-QT style wallets: human-readable aliases, HTML5 wallet work, and a better interface layer.
DIONS expansion
IONS expanded into DIONS: decentralized names, AES-256 oriented encrypted data, messaging, file attachment direction, and application-ready records.
DAPP wallet, identity, ownership, APIs
Wallet work connected identities, avatars, documents, deeds, copyrights, trademarks, proof of ownership, transfers, and API surfaces.
Shade addresses and shuffle staking
Privacy and staking research added optional private-payment direction and better staking participation for smaller holders.
04 / chain stack
What the chain is designed to make possible.
Efficient network security without permanent mining arms-race economics.
Human-readable identity and address records instead of raw keys alone.
User-held data payloads and file-oriented proof records anchored to the chain.
Messaging direction built around key ownership instead of platform custody.
Wallet surfaces that expose the protocol, not only send and receive buttons.
Developer-facing access so the chain can connect to applications and services.
05 / dions 2.0
DIONS 2.0 moves IOC from encrypted records into a programmable protocol layer.
DIONS 2.0 continues the original I/O Coin thesis: names, identities, messages, files, and data should belong to key holders, not platform databases. The upgrade path brings that work toward a DIONS Virtual Machine, where encrypted data payloads and programmable execution can live closer to the base chain.
Open the DIONS 2.0 dossierDIONS data payloads remain the center: records, aliases, messaging, and file-oriented proofs that extend IOC beyond payment movement.
The DVM direction connects IOC's encrypted-data layer with programmable application logic, keeping DIONS as the differentiator.
The current DIONS 2.0 direction points toward Solidity/EVM compatibility so builders can approach IOC without abandoning known developer patterns.
DIONS 2.0 belongs to the same chain record: fair launch, Proof of Stake, IONS, encrypted messaging, identity, wallet surfaces, and APIs.
LayerDIONS data payload
ExecutionDIONS Virtual Machine
Developer pathSolidity / EVM direction
06 / network access
The working resources belong on the front of the site.
explorerLive IOC chain explorer
bootstrapBootstrap chain data package
macOSDIONS Aurora DMG
windowsDIONS Aurora EXE
linuxDIONS Aurora install script
whitepaperIOCoin Whitepaper PDF
apiIOC API reference PDF
sourceIOCoin / DIONS GitHub
wikiI/O Digital Foundation GitBook
archiveWizrig Medium history
dions 2.0Protocol upgrade dossier