AI-native security · Layer 1

AI runs the protocol.
Security is native, not a service.

A Layer 1 where six embedded models audit contracts, weigh every transaction and guard the exchange, every operation is signed in full with a quantum-safe key, and AI agents act through scoped session keys without ever holding your master key.

path of one transactionheight #1,284,331
01

Signed in full

ML-DSA-65 · every field

3,309 B sig
02

Weighed by Sentinel

risk score, same on every node

score 0.07 · pass
03

Voted by stake

Malachite BFT · > 2/3

04

Committed

one state root per block

0x3fa1…c07e
6AI models in the protocol
FIPS 204ML-DSA-65 signatures
< 2 msVMGuardian audit
MalachiteTendermint BFT
Dev log

Latest news

All news →

The problem

Web3 security is a service you buy once. It should be a property the protocol has.

A typical chainone audit, then silence
NeuroChainscored for its whole life
deploytime →
01

Audits are a snapshot

A contract is reviewed once, before launch. Everything it does after that point is unwatched.

02

Security is bolted on

Firms sell a report; the chain itself has no opinion about what runs on it.

03

Quantum risk is postponed

Most chains still sign with curves a large quantum computer breaks, and treat the fix as a future migration.

The protocol, layer by layer

Security is in every layer. None of it is optional.

identity

The address outlives the key

Keys rotate, guardians restore a lost one; role-typed names (.human .node .app .vault .agent) are NFT aliases of the address.

rotate_key · recovery
signatures

Quantum-safe, signed in full

ML-DSA-65 signs every transaction and every vote; a privileged operation is signed over every field it acts on.

FIPS 204 · clear signing
risk

Sentinel · SentinelDex

Every transaction and every exchange operation gets a risk score that every node computes the same way.

pass · hold · owner key
audit

VMGuardian gate

Every contract is scored before deploy, a risky one is refused, and it keeps being re-scored as it runs.

< 2 ms · on-chain cert
execution

Metered WASM · native assets · DEX

wasmi with fuel metering; native assets and a batch-auction exchange live in the state machine itself.

wasmi · AMM
consensus

Malachite BFT per shard

Tendermint safety; proposer by stake; double-sign guard; equivocation means burn and jail.

> 2/3 stake
state

Verifiable state

Merkle state root over every consensus column; new nodes start from snapshots certified by > 2/3 of stake.

41 column families
6 models, on-chain

Small enough to run in every node. Small enough to prove.

The models are part of the node binary, registered through consensus, and every node reaches the same score. Their size is the point: a model this small can be proven, which is where the roadmap goes next.

ConsensusAI
validator trust · jail / slash
10,626
SmartForge
contract studio
6,853
NetOptimizer
routing · shard load
1,765
VMGuardian
pre-deploy gate · monitoring
897
Sentinel
transaction risk · 8→16→8→1
289
SentinelDex
exchange risk · 8→16→8→1
289
parameters per model, linear scale
all 6 together
20,719
parameters

Every one runs inside the node, with no external oracle and no model API to trust.

VMGuardian audit
< 2 ms
browser verifier
115 KB WASM
registration
BFT tx + 2f+1 confirm
How it works

One transaction, five checks, no trusted party.

STEP 01
ML-DSA-65 · 3,309 bytes

Signed in full

The wallet signs every field the operation acts on, under ML-DSA-65. It signs what it shows.

STEP 02
  • ✓signature & key
  • ✓nonce in order
  • ✓balance & gas
  • ✓shard & owner

Ingress validates

The node checks and admits. It writes nothing; every write happens when the block commits.

STEP 03
score 0.05 · pass

Risk is weighed

Low risk passes. Elevated waits with a window to cancel. High needs the owner’s own key.

STEP 04
79%of stake voted

Stake votes

Malachite commits the block when validators holding more than 2/3 of stake sign it.

STEP 05
STATE ROOT0x9c41e0a7 52bd18f3…

Committed, provable

apply_tx writes the state; one root covers it, and anyone can check a proof against it.

Contract security

Audited once is not audited. This runs for the contract’s whole life.

Deploy

Bytecode arrives with the creating transaction.

Analyze

Reentrancy, unbounded loops, memory growth. Over the threshold means refused.

Certify

A security certificate is minted on-chain.

Monitor

Re-scored as it runs; a real shift re-issues the certificate.

1.00.70.40.1refused at deploy above this linedeploy · cert v1v2score shift → certificate re-issuedtime →illustrative
AI and consensus

Where AI may touch consensus, and the one place it never can.

Tendermint safety rests on 2/3 of voting power, and voting power is stake. Changing it would break the Byzantine proof, so AI only works where removing a validator is safe.

● Safe seams

  • Validator trust is computed on-chain from blocks proposed and votes cast
  • Jail and slash: a misbehaving validator’s power goes to zero
  • Equivocation found over gossip is burned and jailed

● Never

  • The 2/3 commit quorum
  • Raising anyone’s voting power
  • Choosing the proposer: that is stake-weighted and deterministic, so every validator agrees
voting power of a validator set · each segment is one validator’s stake
seed = height · 1_000_003 + round → proposerred: jailed → 0
Native exchange

An exchange where a sandwich does not pay.

Native assets and pools live in the state machine. Every block clears each pool once, at one price for both directions, and SentinelDex scores every exchange operation before it runs.

One block, one price

Opposite orders net against each other first. Only the imbalance moves the curve, so a round trip inside one block pays two fees and earns nothing.

orders A → Borders B → Amatched peer to peer200 ↔ 200 · curve untouchedimbalance → pool140 A → B · x·y = ksame clearing price for every order in the block

SentinelDex: mean score by behaviour

Trained on attack classes from published incident analyses. It never refuses: high scores wait or need the owner’s key.

normal swap
0.05
full withdrawal
0.10
honest large swap
0.28
round trip
0.54
batch fill
0.67
issuer dump
0.81
transfer drain
0.87
thin-pool dump
0.93
hold 0.60owner 0.70
passesheld, cancel windowowner’s key
1 pricefor both directions of a pool in a block
min_outmandatory on every swap, signed with it
NROis the fee currency; NRO pairs need a vote
0flash loans: no contract can reach the exchange
AI agents

Your agent can act on-chain. It never sees your master key.

Grant a scoped, revocable session key with its own spending limit. The agent transacts within it, and the riskiest moves still come back to you.

  • Session keys are checked inside consensus, not by a middleman
  • Sponsored gas: a new agent needs no balance to start
  • No self-approval: only the owner’s key confirms a held move
  • MCP server: an LLM agent works as a client, within its grant
master keycold storagegrantsession key300 / 500 NROAI agentvia MCPtransfer · within limitsigned · verified · committedrisky moveowner key onlysponsor poolpays the first gas
key 1alice.humansame addressG1G2G3key rotated · balance and history unchanged
Identity

Lose a key, keep the address.

The keys that control an address live in network state. A key rotates with one signed transaction, and guardians you named in advance restore access without a support desk. The address, balance and history never change.

.human free, from your keys.node validator.app contract.vault multisig treasury.agent AI agent

a purchased name is an NFT alias of its owner’s address

Verifiable AI × interoperability

The first half is running. The second is the roadmap.

Two NeuroChain networks already exchange tokens through an IBC-style light client. Next, the same proofs carry an AI audit: a result backed by a cryptographic proof that travels with the asset.

no relayer is trusted: B checks A itselfNetwork Aescrow · certified blockNetwork Bvoucher creditedvalidator signatures> 2/3 of A’s stakeMerkle proofat the certified heightpkt
Roadmap

5 phases done. Mainnet preparation now.

1
Foundationdone
2
Gas, PQC & hardeningdone
3
WASM VM + VMGuardiandone
4
Sharding + Malachitedone
5
Identity, governance & AI agentsdone
6
Mainnet preparationin progress
7
Verifiable AI × interoperabilityplanned
Phase 6 · now

Mainnet preparation

Green is done, blue is in progress.

Jellyfish Merkle state tree + certified state syncSupply invariant + full invariant auditEvery operation signed in full, clear signingNative assets + batch-auction DEX + SentinelDexPurchased names as NFT aliases, reserved-name registryLoad test and 72-hour soakFormal third-party crypto auditInstallable mobile wallet
Why NeuroChain

Two categories exist today. This sits at the intersection.

Audit-as-a-serviceCertiK, QuantstampPost-quantum chainsNaoris, QANplatformNeuroChainthis chain
Audit is a protocol ruleoff-chain report—✓
Contracts watched after deployper engagement—✓
Post-quantum signatures—✓✓
Every transaction risk-weighed——✓
Agent session keys in consensus——✓
Exchange with uniform batch price——✓
Rust workspaceRocksDB · 41 column familiesML-DSA-65 · FIPS 204Malachite BFTwasmi runtimeCertified state syncDouble-sign guardIBC-style light clientBatch-auction DEXSentinelDexSame crate, server + browserRust workspaceRocksDB · 41 column familiesML-DSA-65 · FIPS 204Malachite BFTwasmi runtimeCertified state syncDouble-sign guardIBC-style light clientBatch-auction DEXSentinelDexSame crate, server + browser
Launch

Be first to know when the network opens

Testnet and app are in active development. Leave your email — we will send a single announcement when the public launch is ready. Telegram stays the day-to-day build log.

One email when we announce the public launch. No newsletter spam. Unsubscribe anytime (reply to the launch email).