The Asentum Thesis
Three problems with current blockchains, the evidence they're real, and the one chain we're building to solve all three.
10 min read
A note first
Why I'm doing this
This is kind of just a rationale to myself, to be honest. But why not share it — why not build publicly.
I've always wanted to build a chain. I spun up Geth on my Mac and played around with devnets, rebuilt little parts of it just for pointless fun really. But I've never really had a reason to tryhard the build. Nobody needed another chain, another Layer-2 that does the same exact thing as 73 others.
Now, with quantum computing on the edge of becoming a reality, I think we actually do need a new chain.
Everything below is my honest account of why. Three problems with the chains we have, the evidence they're real, and what we're doing about it.
Problem 1
The chains we have will implode
The problem
Every major blockchain securing value today signs transactions with ECDSA or Ed25519. Both schemes rest on the discrete-logarithm problem being hard. In 1994 Peter Shor proved that a sufficiently large quantum computer can solve that problem in polynomial time. Not weaken it — break it.
In ten years, if that machine exists, people will derive secret keys from public addresses and empty dormant sleeping whales onto the open market. Bloodshed like we've never seen. And because blockchains are permanent public ledgers, the attack is retroactive — every signature ever written is already archived, already waiting.
The evidence
NIST finalised the first post-quantum signature standard — FIPS 204, ML-DSA — in August 2024. Federal systems have migration deadlines. Major TLS libraries are already shipping hybrid post-quantum handshakes. The NIST Post-Quantum Cryptography program is the primary source. Blockchains, as a category, have not moved.
What we're doing
Every signature on Asentum, from block zero, is ML-DSA-65 (Dilithium3) — the NIST-standardized post-quantum scheme, level 3 security. There is no migration period because there is no classical signature history to migrate from. The cost of building this in from day one is small. The cost of being wrong about the timeline is catastrophic.
Problem 2
The developer pool is 100× too small
The problem
If you want a chain to matter, you need people who can build on it. The blockchain industry has spent a decade asking the rest of the software world to learn its language. Imagine what smart contracts could be capable of if they were written and executed natively in pure JavaScript — the language that already runs every website, every mobile app, most of the internet.
The evidence
22 million+ people write JavaScript. Guess how many active blockchain developers there are? Around 24,000. Source: the 2024 Developer Report. That is a ratio of roughly 1,000 to 1. The largest untapped labor pool in software, and every blockchain has been ignoring it.
What we're doing
Asentum contracts are plain JavaScript. Not transpiled, not a subset, not a Solidity-shaped DSL with curly braces. Real JS, running inside a Hardened JavaScript sandbox, deterministic across CPU architectures. Readable on-chain. Verifiable in a single hash compare. If you've written Node for ten years, you already know enough to ship a contract on Asentum.
Problem 3
Validator decentralisation is mostly a claim
The problem
Current chains claim they are decentralized. In reality, joining a chain as a validator is ruthlessly expensive and dominated by the same three or four massive operators. The hardware floor forces everyone else into renting from AWS, GCP, or Hetzner — which means the network ends up looking, in practice, like a federation of cloud tenants in two countries.
The evidence
Ethereum validators want a server-class machine. Solana's floor is closer to $5,000 in hardware and a gigabit uplink. You can measure the outcome: on every major chain, a handful of operators concentrate a supermajority of stake, and most of them live in a handful of datacenter regions. "Decentralisation" at those thresholds is a marketing claim, not a property of the system.
What we're doing
Asentum is tuned for the median consumer PC — a 4-core laptop with 8 GB of RAM. The Raspberry Pi 4 is the supported floor. 2-second blocks, a rotating ~100-validator BFT committee per epoch, permissionless after genesis. The ceiling on how many independent operators the network can host isn't set by economics — it's set by how many people want to participate. We ship the node as a single binary installer and a desktop app so a non-dev can turn their home PC into a meaningful, incentivised validator in under ten minutes.
The answer
What Asentum is, in one paragraph
A Layer-1 blockchain built end-to-end in JavaScript. Tendermint-style BFT with a rotating ~100-validator committee, permissionless after genesis. ML-DSA-65 signatures everywhere. BLAKE3 hashing, Sparse Merkle Tree state over LevelDB, HTTP peer fan-out for block sync and vote gossip. Smart contracts in Hardened JavaScript with async cross-contract calls (reentrancy structurally impossible), immutable by default, verifiable by hash compare. EIP-1559 fee market with base-fee burn. Cosmos-style delegation with shared slashing. JSON-RPC compatible with the Ethereum tooling ecosystem so MetaMask, ethers.js, and viem work for reads. Tuned for consumer hardware with a Pi 4 floor. Everything above is specified and shipped — not planned. See the research page for the full decisions log.
Right now
Where we are
The public testnet is live at testnet.asentum.com — five validators across three continents, producing 2-second blocks under real BFT consensus. The CLI installer, the Chrome extension wallet, the desktop app, and the contract playground are all usable today. On-chain governance with hard and soft proposals is live. The SDK (@asentum/sdk) is published.
Mainnet is Phase 4 of the rollout. We're publishing the specification before locking the economics because we want the spec to be the thing that gets criticised, broken, and improved — by cryptography researchers, by JavaScript engineers, by validators-to-be, and by anyone who reads a passage of this and thinks "you're wrong about that."
If any of this resonates
The ask
If you write JavaScript and have ever wondered why writing a blockchain contract has to feel so unfamiliar — read the contract model and tell me what would make it feel like home.
If you work in cryptography and have an opinion about lattice schemes, deterministic execution, or the failure modes of BFT committees — read the post-quantum and consensus docs and tell me where they're wrong.
If you run a node at home, or used to, or always wanted to — get on the launch list. The first hundred validators on Asentum will be the people who decided this mattered before it was obvious.
We're building a chain that's meant to last decades. It's going to be built with the people who show up early.
— milkie