OpenZeppelin Expands Audited Smart Contract Tools to TRON
The release adds TRON-specific libraries, upgrade plugins, Contracts Wizard support and an MCP server for AI-assisted development.
OpenZeppelin expanded its audited smart contract libraries and development tools to TRON on Sept. 24, adding network-specific infrastructure for tokens, upgrades, permissions and AI-assisted application development.
The release includes tron-contracts and tron-contracts-upgradeable, which provide components for TRC-20 tokens, access control and upgradeable contracts. TRC-20 is TRON’s fungible-token standard and is compatible with Ethereum’s ERC-20 interface.
Developers can connect the upgrade tools to TronBox, Hardhat and Foundry through tronbox-upgrades, hardhat-tron-upgrades and foundry-upgrades-tron. The tools support UUPS upgrade patterns and TRC-1967 proxies, allowing contracts to be updated without changing their state or address.
Contracts Wizard can generate boilerplate for TRON-compatible contracts, while an MCP server adds tooling for AI-assisted development. The libraries also include role-based permissions and extensions for gasless approvals, supply caps and on-chain voting.
Support for secp256r1 signatures enables passkey-based wallet designs using Face ID, fingerprint authentication and hardware keys. TRON is broadly compatible with Solidity, the programming language used for Ethereum smart contracts, but some Ethereum Virtual Machine capabilities become available on TRON through network upgrades rather than being enabled from the outset.
The TRON-specific libraries and plugins are designed around the network’s current capabilities. They standardize components for security-sensitive functions such as token issuance, access control, governance and contract upgrades, reducing the need for developers to build those elements independently.
“Strong security starts at the foundation. Developers need primitives they can trust on the network they are deploying to,” said Pepe Blasco, an engineering manager at OpenZeppelin.
The components do not secure application logic created around them. Production deployments still require dependency reviews, storage-layout validation, access-control or governance reviews and application-specific testing.
“Security is fundamental to expanding what developers can build across the TRON ecosystem,” said Sam Elfarra, a community spokesperson for the TRON DAO.
