How Asentum Works

Last updated March 20, 2026 · Estimated read time: 12 minutes

1.1 Architecture Overview

Asentum is a Layer 1 blockchain built entirely in JavaScript (Node.js). Smart contracts run in sandboxed V8 Isolates, consensus is Delegated Proof of Stake with 21 active validators, and blocks are produced every 3 seconds. The entire stack — nodes, contracts, tooling — is JavaScript.

1.2 DPoS Consensus

Token holders vote for validator candidates. The top 21 by stake-weighted votes become active validators for a 24-hour epoch. 100 standby validators are ready to fill slots if an active validator goes offline. Finality requires 2/3 confirmation (~6 seconds).

Validators who double-sign or experience excessive downtime are slashed — losing a portion of their staked ASX. This makes honest behavior the most profitable strategy.

1.3 The JavaScript VM (V8 Isolates)

Each smart contract runs in an isolated V8 context — the same engine that powers Chrome and Node.js. Contracts have no access to the filesystem, network, or OS. Determinism is enforced by replacing Math.random() with a seeded PRNG, Date.now() with block timestamps, and disabling all I/O.

This is the same model Cloudflare Workers uses at massive scale — proven, battle-tested, and secure.

1.4 Smart Contract Model

Contracts are ES module classes. State is stored as class properties (auto-persisted). Globals like msg.sender, msg.value, block.number, and block.timestamp are injected. The standard library includes @asentum/token, @asentum/nft, @asentum/dao, and @asentum/math.

1.5 Network Architecture

Nodes communicate via libp2p (the same peer-to-peer library used by IPFS and Filecoin). Chain state is stored in LevelDB, blocks in flat files. The JSON-RPC API is compatible with Ethereum tooling where possible, so existing Web3 libraries work with minimal configuration.

1.6 Developer Tooling