Skip to content
M5Chain network

A Layer 1 that understands markets.

M5Chain is a sovereign, non-EVM-native Layer 1 with finance-aware state and deterministic settlement, built for order books, margin and clearing from the first block.

01Propose02Vote03Commit04Final
Proposer Validator

HelixBFT consensus

Finality you can verify.

Validators take turns proposing blocks in a deterministic order. Stake-weighted votes finalize them, and misbehaviour produces on-chain evidence that is slashed by rule rather than by discretion.

Assured by

HelixBFT

Formal protocol specification, reference model, fault injection and finality traces.

  • Deterministic proposer rotation
  • Stake-weighted voting and finality
  • On-chain evidence and slashing
  • Fault-injection testing

FluxGrid execution

Parallel lanes. Deterministic outcome.

FluxGrid schedules independent transactions across parallel lanes, detects conflicts and re-sequences them deterministically, so every node reaches the same state root regardless of thread count.

Lane 1
Lane 2
Lane 3
Lane 4
Conflict detected · re-sequenced Canonical commit · state root 0x7f3a…c41e

Runtimes

Native performance. Familiar tooling.

NovaWASM

Capability-scoped WebAssembly for native financial applications. Contracts are metered precisely and can only touch the capabilities they are granted.

  • Capability-scoped permissions
  • Deterministic metering
  • Sandboxed execution
  • Developer SDK and toolkit

BridgeCell

An isolated Ethereum-compatible cell with a JSON-RPC boundary, its own state and resource quotas. Existing tools work; the core chain stays non-EVM-native.

  • JSON-RPC compatibility boundary
  • Independent state boundary
  • Resource quotas
  • Pause control

Performance

Built for a million transactions per second.

HelixBFT finality and FluxGrid parallel execution give M5Chain an engineered aggregate capacity of one million transactions per second. Every benchmark we publish comes with its full test conditions.

0

TPS · engineered aggregate capacity

Every benchmark we publish states

  • 1Workload and action type
  • 2Hardware profile
  • 3Validator topology and regions
  • 4Test duration and state growth
  • 5Finality at p50, p95 and p99
  • 6Failure conditions

CrossLock interoperability

Connected, within limits.

Assets move between networks only through registered routes with verified proofs and per-route exposure caps. Any corridor can be paused and recovered without touching the rest of the network.

  • Registered routes only
  • Proof-verified transfers
  • Exposure caps per corridor
  • Pause and recovery drills

Validators

A professional validator network.

Validator lifecycle, sentries, upgrades and governance controls are part of the protocol, with telemetry and fault testing from the first localnet.

  • 01

    Lifecycle and governance controls

  • 02

    Rehearsed upgrade mechanism

  • 03

    Telemetry and fault harness

  • 04

    Explorer and node tooling

Ready when you are.

Open your M5Liquid account in under a minute, or talk to our team about institutional onboarding, liquidity partnerships and integrations.