Nothing found.

Latest stories

Solidity Hot Reloading Using ZepKit

​​​​ZepKit provides a great start for DApp development on Ethereum. Today, we are happy to announce the release of…

Read More

Technical Description of Critical Vulnerability in MakerDAO Governance

While working on an audit for the Coinbase team, we found a critical vulnerability in the DSChief contract of the…

Read More

MakerDAO Critical Vulnerability Notice

While working on an audit for the Coinbase team, we found a critical vulnerability in one of the DappHub library…

Read More

Our most popular audit reports

Nothing found.

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. The audited project can be…

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!

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…

Deconstructing a Solidity Contract — Part V: Function Bodies

The function body is precisely what the function wrappers detour to, after unpacking the incoming calldata. By the time a function body is executed, the function’s arguments should be sitting…