ioc protocol upgrade / dions architecture / active testnet research

DIONS 2.0 Protocol Report

A technical view of the I/O Coin upgrade path: deterministic Proof-of-Stake behavior, execution zones, native identity, encrypted messaging, data availability, bridge mechanics, lightweight participation, and post-quantum direction.

Portal source View diagrams IOC source

DIONS / RC telemetry May 2026 source material

RPC150methods

Tests741/741core suite

Targets13binaries

RuntimeC++20rewrite

Base continuity: Fair-launch IOC chain since 2014
Legacy DIONS: Aliases, encrypted messages, data/file paths
Upgrade vector: Fixed cadence, zones, DID, PQC, DA, bridge

01 / what this page is

This is the DIONS 2.0 technical layer, inside the I/O Coin story.

The old DIONS work already gave IOCoin human-readable aliases, alias-linked data, public and encrypted messaging APIs, file transfer paths, AES-256/RSA-4096 encryption, Shade privacy APIs, and Proof-of-Stake chain operation.

DIONS 2.0 does not replace that history. It tightens the chain model and expands the application surface: deterministic block cadence, hardened indexes, dual execution zones, W3C-style identity, post-quantum cryptography, data availability, bridge mechanics, WebSocket/event APIs, and a light-client participation path.

02 / system architecture

System map: L1 settlement plus execution and data layers.

L1 / DIONS base layer 30s target cadence

PoSEnhanced stake consensus

Checkpoints, finality threshold, deep reorg protection, validator states.

IdentityW3C DID direction

Aliases, agents, devices, and key-held identity records.

MessagingEncrypted data layer

Direct messages, channels, shadow messaging, file/data transfer paths.

PQCHybrid crypto track

Dilithium, Falcon, Kyber, and classical compatibility lanes.

DAReed-Solomon sharding

64 data shards, 32 parity shards, light-client sampling.

BridgeHTLC / relayer path

Lock, attest, mint, burn, unlock, reserve accounting.

88L1 TPS

11,000+with zones

150RPC methods

100 MBlight disk

EVM zone1,000+ TPS

Solidity / Vyper
evmone execution engine
eth_* JSON-RPC layer
EIP-1153, EIP-2200, EIP-2929 track

SVM zone10,000+ TPS

Rust / C BPF programs
Account model and PDAs
Cross-program invocation
Challenge / dispute path

03 / transition map

Before, now, and what becomes new in the upgrade path.

Feature area	Legacy DIONS / IOCoin	DIONS 2.0 path	New surface
Consensus model	Variable cadence under legacy network conditions	Fixed 30-second target cadence with stricter liveness behavior	Modular commitments: stateRoot, dataRoot, zoneRoot
Alias resolution	Alias identity and data already present	O(1) LevelDB indexed resolution	Hardened deterministic index path
Messaging	Public/encrypted messaging APIs	Encrypted/plain/shadow messaging with consistency gates	Expanded channel lifecycle and policy controls
Files/data	Upload, download, transfer paths existed	Quota-governed deterministic data behavior	DA/sharding with Reed-Solomon direction
Cryptography	Classical encryption/signing assumptions	Hybrid crypto paths integrated in runtime and tests	Dilithium, Falcon, Kyber readiness track
Execution	No native smart-contract execution zones	EVM and SVM execution paths integrated	Solidity and Rust-style application lanes
Bridge	No mature wrapped-asset bridge stack	ECDSA signing, HTLC, relayer mechanics	IOC20 / wrapped IOC interop route
Participation	Full wallet/node model	Light client and PoP relay paths	Headers-only sync and zero-balance relay rewards

04 / chain comparison

DIONS 2.0 is measured against current L1 expectations.

	Ethereum	Solana	DIONS 2.0
L1 TPS	15-30	~400	88
With zones	Thousands through rollups	~4,000	11,000+ through EVM + SVM
Post-quantum	None	None	Dilithium + Falcon + Kyber
Native identity	ENS adjacent / off-chain	No	W3C DID Core 1.0 direction
Native messaging	No	No	AES-256 + RSA-4096 path
Light client	Sync committee model	Limited	Native binary, headers-only, ~100 MB disk
Earn from zero	No	No	PoP relay reward path

05 / execution

Two execution zones, one IOC continuity layer.

EVM zone

Ethereum-compatible contract lane.

Solidity / Vyper contracts
evmone execution engine
1,000+ TPS target lane
Full eth_* JSON-RPC surface
State roots posted back to L1

SVM zone

High-throughput program lane.

Rust / C BPF programs
Account model and PDAs
Cross-program invocation
Dispute and challenge-response layer
Zone root settlement to L1

06 / data availability

Data availability: 64 data shards plus 32 parity shards.

64 data shards 32 parity shards recover from any 64 of 96

Light client sampling: 20 random shards
Detection confidence: 99.99%
Retention window: 10,000 blocks
Per-node storage: 1-10% direction

07 / cryptography

Post-quantum track and device profiles.

Algorithm	NIST level	Key size	Signature	Use case
Dilithium-2	2	1,312 B	1,387 B	General purpose
Dilithium-3	3	1,952 B	2,044 B	Robot / server
Dilithium-5	5	2,701 B	3,293 B	Maximum security
Falcon-512	1	897 B	~500 B	Compact IoT
Falcon-1024	5	1,793 B	~800 B	High-security IoT
Kyber-512/768/1024	1/3/5	800-1,568 B	KEM	Key encapsulation

IOT_MINIMALKyber-512 + Falcon-512

ROBOT_STANDARDKyber-768 + Dilithium-3

SERVERKyber-1024 + Dilithium-5

08 / identity + messaging

DID records, aliases, devices, agents, and native encrypted messaging.

Agentdid:dions:agent:bot1

Autonomous entity. Owns and delegates to devices.

Devicedid:dions:device:sensor7

Hardware identity delegated from an agent or account.

Aliasdid:dions:alice

Human-readable identity linked to wallet ownership.

{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:dions:agent:bot1",
  "verificationMethod": [{
    "type": "EcdsaSecp256k1VerificationKey2019"
  }],
  "service": [{
    "type": "DionsMessaging",
    "serviceEndpoint": "dions://msg/bot1"
  }]
}

09 / moving bridge diagram

Wrapped IOC bridge mechanics and exchange-readiness path.

native IOC lock events validator attestations wIOC mint / burn / unlock accounting

10 / moving light-client diagram

Light-client wallet path: verify, sample, participate.

headers-only sync DA sampling participation rewards

11 / network + build

Protocol parameters and build surface.

Network ports

Mainnet P2P: 33764
Mainnet RPC: 33765
Testnet P2P: 33763
Testnet RPC: 33766
WebSocket: 33776
Chain IDs: 8377 / 8378

Build targets

cd build
cmake --build . -j$(nproc)

# dions2d, dions2-light,
# dions-cli, dions-explorer,
# dions2-migrate, dions-relayer,
# dns seeder, test binaries

12 / evidence

Security and RC evidence from the portal material.

Core suite741/741

Passing in the current RC update material.

Target matrix37/37

Fresh repo-root local target pass.

Validator gate4 nodes

Reachable, same commit, finalized parity clean.

Remaining gaterestart/catchup

Controlled validator restarts and endurance hardening remain release-critical.

13 / source material

Follow the source record.

dions portalDIONS 2.0 Architecture Portal ioc sourceIOCoin / DIONS GitHub whitepaperIOCoin Whitepaper PDF apiIOC API reference PDF wikiI/O Digital Foundation GitBook iocoinReturn to main site