Nothing found.

Latest stories

PoolTogether Audit

The PoolTogether team asked us to review and audit the system. We looked at the code and now publish our results.

Read More

Aave Protocol Audit Summary

The Aave team asked us to review and audit a pre-production version of their protocol.

Read More

Aave Protocol Audit

The Aave team asked us to review and audit a pre-production version of their protocol. We looked at the code and now…

Read More

Our most popular audit reports

Nothing found.

SEE ALL >
More stories

Solidity Compiler Audit

The Augur team and the Ethereum Foundation (through a joint grant) asked us to review and audit the Solidity compiler. We looked at the code and now publish our results.

Announcing the ZEP Token Private Beta

Today we are excited to announce the ZEP Token Private Beta for ZeppelinOS — a network that uses economic incentives to maintain a healthy ecosystem of secure smart contract applications.

Introducing ZeppelinOS 2.0

The platform for developing, deploying, and operating smart contract projects.

Participate in Zeppelin’s Puzzle Game to Celebrate Devcon4!

After the fun we had with last year’s Ethernaut hacking game, we’re releasing EthHunt, a new game to celebrate Zeppelin’s sponsorship of Devcon4!

OpenBazaar’s Escrow Audit

The OpenBazaar team asked us to review and audit their Escrow contract, one of several in their framework. We looked at the code and now publish our results.

Getting started with OpenZeppelin-eth

These are great times for smart contract development. The pieces for Ethereum 2.0 are coming together, and new tools and practices are blooming.

Announcing OpenZeppelin 2.0

A stable, audited, and fully tested package for smart contract development

Open source collaboration in the blockchain era: EVM packages

Smart contract development is still in its early days. We’re all still trying to figure out what it will look like and how to polish the developer experience.

The Global Coordination Machine

Few applications need blockchains. Distributed consensus makes each computational step very expensive. Only apps for which users are willing to pay such a cost will make sense in the new…

Deconstructing a Solidity Contract — Part VI: The Metadata Hash

In the last article, we noticed that the runtime bytecode generated by the Solidity compiler appends a strange structure after the function bodies block. You can see this in the deconstruction…

More stories

Solidity Compiler Audit

The Augur team and the Ethereum Foundation (through a joint grant) asked us to review and audit the Solidity compiler. We looked at the code and now publish our results.

Announcing the ZEP Token Private Beta

Today we are excited to announce the ZEP Token Private Beta for ZeppelinOS — a network that uses economic incentives to maintain a healthy ecosystem of secure smart contract applications.

Introducing ZeppelinOS 2.0

The platform for developing, deploying, and operating smart contract projects.

Participate in Zeppelin’s Puzzle Game to Celebrate Devcon4!

After the fun we had with last year’s Ethernaut hacking game, we’re releasing EthHunt, a new game to celebrate Zeppelin’s sponsorship of Devcon4!

OpenBazaar’s Escrow Audit

The OpenBazaar team asked us to review and audit their Escrow contract, one of several in their framework. We looked at the code and now publish our results.

Getting started with OpenZeppelin-eth

These are great times for smart contract development. The pieces for Ethereum 2.0 are coming together, and new tools and practices are blooming.

Announcing OpenZeppelin 2.0

A stable, audited, and fully tested package for smart contract development

Open source collaboration in the blockchain era: EVM packages

Smart contract development is still in its early days. We’re all still trying to figure out what it will look like and how to polish the developer experience.

The Global Coordination Machine

Few applications need blockchains. Distributed consensus makes each computational step very expensive. Only apps for which users are willing to pay such a cost will make sense in the new…

Deconstructing a Solidity Contract — Part VI: The Metadata Hash

In the last article, we noticed that the runtime bytecode generated by the Solidity compiler appends a strange structure after the function bodies block. You can see this in the deconstruction…