Loading... CX3 VM Service
CARBONX3 VM SERVICE
Version 1.0.0  |  Smart Contract Execution  |  JS + WASM Runtime  |  Mersolution Technology
Sandboxed Contract Execution & Compilation Engine
SERVICE CX3VM
STATUS Operational
ENGINE JS + WASM
POOL —
UPTIME —
Digital Footprint
Digital · estimate
— CO₂e
CX3VM service · swd-v4 · estimate
GREEN HOSTING —
DATA SIZE —
ENERGY —
GRID COUNTRY —
Runtime Status
12 components
VM Pool Manager Active
Execution Router Active
JS Executor Active
WASM Executor Active
CX3Script Compiler Active
Compile Cache Active
API Auth Active
Rate Limiter Active
Request Validator Active
Circuit Breaker Closed
Enterprise Hooks Idle
Runtime Metrics Internal
Pool Statistics
Idle
METRICVALUEDETAILS
Pool Size—Total worker instances
Idle—Available for executions
Busy—Currently executing
Queued—Waiting for free worker
Execution Latency
—
METRICVALUEDETAILS
P50— msMedian latency
P90— ms90th percentile
P95— ms95th percentile
P99— ms99th percentile (tail)
Execution Router
0 executions
METRICVALUEDETAILS
Total Executions0All-time dispatch count
JS Executions0JavaScript contracts
WASM Executions0WebAssembly contracts
Route Errors0Failed dispatches
CX3Script Compiler
Idle
METRICVALUEDETAILS
Cache Size—Compiled artefacts cached
Hit Rate—Cache effectiveness
Compile Timeout— msWall-clock limit
Batch Concurrency—Parallel compile slots
Security & Limits
Enforced
METRICVALUEDETAILS
API Auth—Authentication required flag
API AccessCredentialedAuthenticated service calls only
Rate Limit—Requests per window
Auth Failures0Rejected requests
Health & Readiness
—
PROBERESULTDETAILS
/health—Liveness probe
/ready—Readiness probe
/info—Status metadata
Last Check—Time of last poll
Process & Memory
METRICVALUEDETAILS
Node Runtime—JavaScript engine version
Platform—Operating system / architecture
Heap Used—V8 heap utilisation
RSS—Resident set size
About CX3VM

CX3VM is the standalone smart-contract execution engine for the CarbonX3 platform. It runs as a separate process, isolated from the blockchain node. Validators call it to run contract deploys and calls while they apply a block, so it is part of block processing, but it does not produce, sign or vote on blocks.

Contracts execute in a sandboxed JS or WASM runtime with enforced resource limits. Compilation and execution are available only to authenticated platform services.