Nethermind Security

Comprehensive security from @Nethermind, from audits to formal verification. Book now:

[Nethermind Security @NethermindSec]

Your team takes the break. We take the audit.

A few slots open July 1 — August 15. Adjusted rates. AuditAgent Pro included so the codebase is ready before we start.

Smart contracts and ZK circuits.

https://t.co/5lkctca8Ia

[Nethermind Security @NethermindSec]

@arcxtrade https://t.co/R89CYsA1s2

[Nethermind Security @NethermindSec]

We completed a security review of @arcxtrade, a yield-decomposition protocol on Starknet that settles across chains by bridging USDC into Wildcat markets through CCTP. The review covered the full Cairo and Solidity codebase, with close attention to the token decomposition model and the cross-chain settlement path. The higher-severity findings were fixed ahead of the beta.

[Nethermind Security @NethermindSec]

The three places contracts read price, and what holds up: https://t.co/neSiO224u5

[Nethermind Security @NethermindSec]

In 2024, an attacker manipulated a lending protocol's oracle into valuing a single token at roughly $1.37 trillion. The oracle worked as designed. It derived the price from a DEX pool, and a flash loan moved that pool for a single block, so the reported price was the one the attacker chose.

Reading a price directly from a pool is the obvious error, and most experienced teams avoid it. The harder failures are the ones that pass review. A staleness threshold set too high, so an outdated price is still accepted as current. An L2 feed that reads as fresh while the sequencer is down. A TWAP that resists cheap manipulation but lags a fast market enough to leave an exploitable window.

Most teams know an oracle can be manipulated. Confirming that the safeguards already in place actually hold is harder, and it's most of what an audit does here.

[Nethermind Security @NethermindSec]

The codebase was the Bloxchain Protocol by @particle_cs, a smart-contract framework built so one compromised key can't act alone. Full report: https://t.co/nQb8Ltm6qE

[Nethermind Security @NethermindSec]

Everyone's arguing about whether AI replaces security audits. We stopped arguing and ran it: one codebase, three layers, and we tracked what each one actually caught.

AuditAgent (our AI scanner, runs while you build) and AgentArena (independent agents competing to break the same code) cleared the high-frequency stuff early. The bugs that show up in codebase after codebase, gone before anyone senior opened the repo.

So by the time our auditors started, the easy surface was clean. They spent their time on the bugs you can't pattern-match. Things like an external call that ran before the check meant to authorize it. Design-specific, the kind you only find by reasoning through the whole system.

Both camps in this fight are only half right: AI doesn't shrink the audit, it tells the audit where to look. And the audit finds what no scanner ever will.

You don't pick one. You run them in order.

[Nethermind Security @NethermindSec]

It carries context across scans, surfaces more meaningful findings, and you can review and adjust what it remembers. A pre-audit baseline you run while you build, ahead of a comprehensive audit.
https://t.co/EYDojLtS8G

[Nethermind Security @NethermindSec]

Most AI scanners start every run from zero. AuditAgent now keeps a per-project memory. Each scan builds on what it already learned about your codebase, so repeat runs get sharper instead of repeating themselves.

[Nethermind Security @NethermindSec]

Full talk: https://t.co/TVAvQo2c28

[Nethermind Security @NethermindSec]

A ZK circuit can do exactly what it's supposed to and the system around it still gets drained. The risk lives in what the protocol assumes the proof means. Michael Belegris on the bugs our ZK audit team keeps finding: https://t.co/Z6wY2lE0Dr

[Nethermind Security @NethermindSec]

Your team takes the break. We take the audit.

A few slots open July 1 — August 15. Adjusted rates. AuditAgent Pro included so the codebase is ready before we start.

Smart contracts and ZK circuits.

https://t.co/5lkctca8Ia

[Nethermind Security @NethermindSec]

@Uniswap Full case study: https://t.co/E2QNpgXhze

[Nethermind Security @NethermindSec]

Uniswap ran a free AuditAgent scan, an AgentArena competition on UniswapX, and adopted the AuditAgent Business Plan in three months. Cody Born, Principal Engineer at @Uniswap, on what AuditAgent changed in their development workflow:

[Nethermind Security @NethermindSec]

@0xKalzak Pre-audit tools handle the surface layer. AuditAgent flags common vulnerability patterns and dead code so the audit goes deeper from day one. Included with audit slots between July 1 and August 15. Reduced rates: https://t.co/1eMm08NUeR

[Nethermind Security @NethermindSec]

Auditors aren't QA.

When the first days of an engagement go to integration bugs the team would catch on testnet, that's time off the review. When pass one goes to dead code and common vulnerability patterns, that's time not spent on bugs only auditors can find.

[Nethermind Security @NethermindSec]

Full guide on audit prep from @0xKalzak: https://t.co/P5OcgsAzip

[Nethermind Security @NethermindSec]

@lagoon_finance Sequential audits caught these before production. One audit at one version wouldn't have.

Case study: https://t.co/TYhVb1lT1k

[Nethermind Security @NethermindSec]

Auditing ERC-7540 vaults is different from auditing ERC-4626. Settlement happens in a different block than the request. Bugs in the gap can leave users mispriced, locked out of exits, or settled into the wrong cycle.

Standard audit playbooks miss them.

[Nethermind Security @NethermindSec]

@lagoon_finance The work covered pending-state accounting transitions, NAV update timing during synchronous deposits, and economic edge cases at feature interactions.

The most consequential issues became reachable only when new features layered onto existing ones.