New research: Price-oracle manipulation: what a pre-deployment check can catch, and what it can’t
Report an issueGet a demo

In design Smart Contract Verification

Smart contracts, verified before they’re deployed.

An antivirus for the blockchain: upload a contract, get a security report on what it can really do, and deploy only the version that passed. We are designing it now with early partners. Nothing reaches the chain unchecked.

This opens your email app. Or write to [email protected]. We only use your email to reply (privacy).

How it will work

One extra step between compile and deploy

  1. Smart contractYour source
  2. CompileBytecode and ABI
  3. ValidateEvery check below
  4. Verified bytecodeFiltered and reported
  5. DeployContract address
The engine

Four independent checks, one report

Each check answers a different question. A contract ships only when all of them agree.

Contract validator

“This contract cannot be hacked.”

Decompiles the EVM bytecode, infers what it actually does and checks it against security rules and invariants. Symbolic execution and formal proofs are next.

Contract antivirus

“This contract is not a virus.”

Matches the bytecode against known malicious signatures and external scanners, so a payload that harms the chain never gets deployed.

AI review

“Here is what to fix.”

A model reads the contract for risky logic the rules miss, and a correction model proposes a safer version for you to review.

Wallet reputation

“Who are you about to trust?”

Scores the wallets and contracts your code will interact with, based on their past transactions.

+Planned rule setexamples
NG_REENTRANCYViolationDetects unprotected external calls made before state updates
NG_DELEGATECALLViolationDisallows dangerous uses of delegatecall
NG_ETHER_LEAKViolationEnsures fallback functions don’t leak ETH
HAS_OWNER_CHECKComplianceEnsures only the owner can execute sensitive functions
NG_TX_ORIGINViolationRejects tx.origin used for authentication
INVARIANT_STORAGEHeuristicWarns if critical storage slots are writable by unknown code

What you get back

Every validation returns the same report, so a team can gate deployment on it in CI or in the browser.

  • Warnings
  • Violations
  • Compliance
  • Score
  • Recommendation

Planned interfaces: a web app with wallet sign-in, a CLI and an API (upload, validate, deploy).

Roadmap

From agent payments to the protocol

We start where the risk is newest, AI agents that pay on their own, and move down the stack until verification is part of the chain itself.

  1. NowPrototype

    Agent payment verification

    Intent, terms and spend checks in front of the signer. Working prototype, now onboarding design partners.

  2. Stage 1In design

    Verification gateway and API

    A web app, CLI and API: connect a wallet, upload a contract, get a security report, then deploy.

  3. Stage 2Roadmap

    Layer-2 validity proofs

    Run validation off-chain and attach a STARK-style proof that it ran, verified when the contract reaches the chain.

  4. Stage 3Roadmap

    Protocol-level validation

    Validators take part in checking contract contents, rewarded for every verification they perform.

Ready to see MagiChain in action?

We’re onboarding a small group of design partners building agentic payments and on-chain products.

This opens your email app. Or write to [email protected]. We only use your email to reply (privacy).