Why Valdium
Estimated read time: 6 minutes
TL;DR
Valdium is a post-quantum, JavaScript-native Layer-1 blockchain. Every signature is ML-DSA-65 from genesis. Smart contracts are plain JavaScript running in a Hardened sandbox. Validators run on consumer hardware — a Raspberry Pi 4 is the supported floor.
In one paragraph
Valdium is a Layer-1 blockchain whose reference node is written entirely in JavaScript, whose smart contracts are written in JavaScript and execute in a deterministic Hardened JavaScript sandbox, whose signatures use NIST-standardized post-quantum cryptography from genesis, and whose validators run on consumer hardware — with a Raspberry Pi 4 as the supported floor. It uses Tendermint-style BFT consensus with a rotating ~100-validator committee, exposes a JSON-RPC interface compatible with the EVM tooling ecosystem, and is permissionless after genesis.
The three bets
Valdium is built on three architectural bets that the rest of the industry has either ignored or postponed.
Bet #1 — Cryptography
Post-quantum from day one
Every blockchain in production today uses elliptic-curve signatures that a future quantum computer can break. Valdium uses NIST FIPS 204 ML-DSA-65 (Dilithium3) from genesis. No migration period. No legacy classical signatures. The chain is built to outlast the cryptography securing every other Layer-1 today.
Read the spec →Bet #2 — Smart Contracts
Plain JavaScript, with the bugs removed
Contracts on Valdium are plain JavaScript, deployed as source on-chain (no compiler to trust), immutable by default (no hidden upgrade keys), verifiable in a single hash compare, and async between contracts (reentrancy is structurally impossible). The contract platform JavaScript developers should always have had.
Read the spec →Bet #3 — Decentralisation
Validators on real hardware
Valdium is tuned for the median consumer PC — 4-core CPU, 8–16 GB RAM, SSD, residential broadband. The Raspberry Pi 4 is the supported floor. The ~100-validator committee size is the load-bearing design choice that makes post-quantum signatures fit inside that bandwidth budget. The result is a network that can actually be run by individuals from home.
Read the spec →Why now
Three things became impossible to ignore at the same time. NIST standardised a post-quantum signature scheme in August 2024 and almost nobody in the blockchain industry started building with it. A decade of smart contract bugs has not made smart contracts meaningfully safer to write. And "decentralisation" on the chains we admired had quietly become "ten data centres in three regions."
None of those problems is unsolvable. Each is solvable individually. Valdium is the bet that they're more valuable solved together than separately.
What Valdium is not
The non-goals are as important as the goals:
- Not a TPS chase. We're not optimising for raw throughput. The design target is decentralisation and security, not benchmark wins.
- Not a Solidity or Rust VM. Valdium contracts are plain JavaScript running in a deterministic sandbox. The JSON-RPC surface is standard JSON-RPC 2.0, so generic clients adapt with a thin shim — but contract code itself is JavaScript, not Solidity or Rust.
- Not privacy or ZK in v1. Privacy features are deliberately deferred. The chain is fully transparent.
- Not sharded or L2-native in v1. A single, simple, well-understood chain ships first.
- Not bridged in v1. Cross-chain bridges are deferred until the security model is solid.
Where to go next
- Read the full thesis — the longer-form essay version of this page
- Post-Quantum Cryptography — the canonical Dilithium3 spec
- Smart Contracts — the four-pillar contract model
- The research repository — every locked-in design decision with rationale