The Smart Contract Security Standard puts into writing the best practices we advocate for every day at OpenZeppelin.
Glad to have contributed to formalizing this into something that projects can adopt and auditors can attest to.
Smart contract security requires lifecycle-level thinking, not just point-in-time snapshots π
OpenZeppelin contributed to the new @blockchainssc Smart Contract Security Standard to support establishing a chain-agnostic baseline for full application-layer security.
1/ Introducing OpenZeppelin Contracts CLI βοΈ
Scaffold secure smart contracts from your terminal, built on the same battle-tested generators powering over $35 trillion in onchain value.
One command, zero setup.
@ksatyarth2@OpenZeppelin These give agents the context to follow safe patterns, including how to use upgrades plugins for validations. Better informed rather than autonomous.
Introducing OpenZeppelin Skills π€
In the first of a series of releases, we're dropping 9 skills to give AI agents authoritative, up-to-date knowledge of OpenZeppelin Contracts libraries for secure smart contract development, setup, and safe upgrades.
https://t.co/kS0eTJxPJ1
ERC-7984 is now live in the OpenZeppelin Contracts Wizard π
Developers can generate confidential fungible tokens in seconds using Zama's FHE, keeping balances and transfers private by default.
https://t.co/RjGnJrRP0J
Born in Argentina, @OpenZeppelin went from LATAM roots to global security standard. Its libraries define ERC best practices and power thousands of apps, evidence that world-class infra can start in Buenos Aires and scale to secure the internet of value.
https://t.co/tZ24Hr9kZ9
π¨ Calling all smart contract dev friends! π¨
Iβm gathering feedback on OpenZeppelin Contracts and would love your insights.
π Survey link (2 mins):
https://t.co/NzYrwRaNzb
Introducing the Contracts UI Builder β‘
Scaffold a frontend for any deployed contract in a few clicks β select contract functions and export an auto-generated React app with:
β’ Built-in wallet connect
β’ Multi-network support
β’ Zero frontend coding
https://t.co/tHn9YRg3Nf
@Montyly@josepchetrit@OpenZeppelin Some categories and features are conservatively marked as experimental, as they import from https://t.co/ljTzXk4I8k which have different security considerations, but we are in the process of moving many of these into the audited libraries.
@Montyly@josepchetrit@OpenZeppelin The secure aspect is in the generation of the initial templates which are not vibe coded, but instead uses the same code generation logic as https://t.co/PJAtzCt7FC with the same options and results. /
@Montyly@josepchetrit@OpenZeppelin The tools are designed to include using OpenZeppelin libraries as much as possible, and are reviewed and tested to ensure they properly integrate different features together in the resulting contract.
@Montyly@josepchetrit@OpenZeppelin Hi @Montyly, great question! This shifts the responsibility of writing code from the agent to the underlying tools. The agent determines what contracts and features it wants, then invokes the tools which perform the code generation. /