NEST automates LDO buybacks funded by Lido DAO treasury earnings. Our security review covered the contracts, the fixes, and the verified mainnet deployment.
Glossary definition
Deployment verification confirms that what was audited is what runs in production: runtime bytecode, constructor arguments, and deployment parameters.
Deployment verification confirms that what was audited is what runs in production. The deployed code can differ from the reviewed code: a different commit gets deployed, constructor arguments differ, or parameters end up different from the intended values. The verification checks each of these: the runtime bytecode of every deployed contract is compared against a build of the reviewed commit (excluding the compiler’s metadata hash, which varies by build environment), constructor arguments are decoded and checked, and deployment parameters are checked against the values that were intended — for example, the governance proposal that authorized the deployment, where one exists.
The Lido NEST audit summary shows a deployment verification covering nine mainnet contracts.
Used in context