Asentum

Concepts

Why Asentum

Estimated read time: 6 minutes

In one paragraph

Asentum 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 Ethereum tooling ecosystem, and is permissionless after genesis.

The three bets

Asentum 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. Asentum 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 Asentum 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 (no third-party verification middleman), and async between contracts (reentrancy is structurally impossible). The contract platform JavaScript developers should always have had.

Read the spec →

Bet #3 — Decentralization

Validators on real hardware

Asentum is tuned for the median consumer PC — 4-core CPU, 8–16 GB RAM, an 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, not by data center operators.

Read the spec →

Why now

Three things became impossible to ignore at the same time. NIST standardized 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 "decentralization" on the chains we admired had quietly become "ten data centers in three regions."

None of those problems is unsolvable. Each is solvable individually. Asentum is the bet that they're more valuable solved together than separately.

What Asentum is not

The non-goals are as important as the goals:

  • Not a TPS chase. We're not optimizing for raw throughput. The design target is decentralization and security, not benchmark wins.
  • Not bytecode-level EVM compatibility. JSON-RPC compatibility means MetaMask, ethers.js, and viem work — but Solidity contracts don't run unmodified. Contracts must be JavaScript.
  • 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