All Solutions
12

Deployment Audits

Deployment audits for Solana, EVM and Move protocols. We verify the release build, the launch sequence and the multisig transactions before your code goes live.

REQUEST A DEPLOYMENT AUDIT

THE CHALLENGE

An audit reviews code at a commit. Launch day runs a binary.

The deployed program is built by a specific toolchain, initialized by scripts, configured with parameters and upgraded through a multisig. Each of those steps can break audited code: a compiler version that pushes an instruction past its stack limit, an initialization anyone can front-run, a release flag that changes more than it should, an upload that does not match the reviewed source.

A deployment audit checks the release itself, so the code on-chain is the code that was audited.

HOW IT WORKS

How a deployment audit runs

Ten steps, from the release commit to on-chain verification. They catch bugs that only appear in the release build, the deploy order or the multisig transaction, before launch day.

4 phases10 steps

Phase 1: Scope the release

After the audit, before launch

01

Release scope

Adevar Labs and client

Release commit, feature flags, deploy scripts, init parameters, multisig transactions and the exact toolchain you build with.

02

Diff against the audit

Adevar Labs

Every change since the audited commit reviewed. A flag-only release is checked to be flag-only.

Phase 2: Build and rehearse

Days before launch

03

Reproducible build

Adevar Labs

The release rebuilt with your toolchain in a verifiable build, so the hash you deploy can be reproduced.

04

Fresh deploy rehearsal

Adevar Labs

Deployed from scratch on a fork or devnet, then initialized and run through every instruction, upgrade and migration path.

05

Launch sequence review

Adevar Labs

Deploy, initialize, seed and upgrade order checked for front-running, griefing and empty-pool attacks.

Client receives: Release findings as they are confirmed

Phase 3: Fix and sign off

Before launch day

Repeats · Until the release is clean

06

Release fixes

Client

Issues fixed on the release branch, with a new build hash.

07

Re-check

Adevar Labs

The new build reproduced and the rehearsal run again.

Repeats until the rebuilt release passes the rehearsal.

08

Transaction review

Adevar Labs

Multisig payloads decoded before signing: program, buffer, authorities and parameters match the plan.

Client receives: Launch sign-off

Phase 4: Launch and verify

Launch day

09

Deploy

Client

Your team runs the agreed sequence through its multisig.

10

On-chain verification

Adevar Labs

Deployed bytecode matched to the verified build; authorities, configuration and initial state read back.

Client receives: Deployment report

Applies to new deployments, upgrades and migrations of audited code.

FAQ

Frequently Asked Questions

Ready to get started?

Tell us about your project and we'll scope the right engagement for your team.

REQUEST A DEPLOYMENT AUDIT