Voidnaut is built for pre-damage detection.

The difference is timing. Most tools explain the attack after execution. Voidnaut is designed to interrupt the decision before execution.

TimingVoidnautOthers

TimingPreemptiveReactive

Data sourceMempool-basedOn-chain only

Core signalIntent detectionCode analysis

OutcomeBefore damageAfter damage

Detection preview

What follows is a sample of the product workflow: how a high-risk pending deployment would be analyzed, what flags surface, and how output is structured for human review or machine action. Voidnaut is currently in pre-launch development.

Sample input

0x91e4...db44 · Ethereum · Mempool mode

Request early access

Sample analysis output

Malicious intent likely before launch

82 / 100 risk score

The model sees overlapping indicators tied to exit traps, deployer-linked wallet spread, and staged liquidity manipulation.

Primary flagMutable sell fee path
Secondary flagDeployer-linked wallets concentrating supply
Execution windowAlert raised before first liquidity event

API and integration surface

Voidnaut is designed to wire into bots, risk engines, and internal monitoring with minimal surface area. The integration layer below reflects the planned API shape.

Token scan endpoint

Query a contract, pair, or pending deployment and receive a normalized risk object built for machine decisions.

POST /v1/scan\n{\n  "chain": "ethereum",\n  "target": "0x91e4...db44",\n  "mode": "mempool"\n}\n\n200 OK\n{\n  "riskScore": 82,\n  "verdict": "block",\n  "flags": ["mutable_sell_fee", "wallet_cluster"]\n}

Webhook alerts

Ship high-risk detections into Telegram, Slack, Discord, or internal incident pipelines the second the threshold is crossed.

Bot integration

Attach Voidnaut to sniper guards, launch monitors, or due diligence automations that need a fast allow-or-block verdict.