Binance-Peg Dogecoin Token (DOGE) Smart Contract Audit

Project Background

This project implements an upgradeable proxy architecture for BEP20/ERC20 smart contracts using the transparent proxy pattern. It is built on standardized proxy contracts provided by OpenZeppelin to ensure security, reliability, and industry best practices.

The architecture separates contract logic from storage, allowing the underlying implementation to be upgraded without redeploying the proxy contract or losing state. The core Proxy contract forwards all external calls to the current implementation using the delegatecall opcode.

The UpgradeableProxy contract stores the implementation address in a standardized EIP-1967 storage slot, preventing storage collisions with the implementation contract. The TransparentUpgradeableProxy extends this functionality by introducing an admin-controlled upgrade mechanism.

Only the designated admin can perform upgrades or modify proxy configurations, ensuring controlled and secure contract evolution. Regular users interact seamlessly with the implementation through fallback delegation, without being aware of the proxy layer.

To prevent function selector conflicts, the transparent proxy pattern ensures that admin-only functions are inaccessible to regular users and that admin accounts cannot accidentally invoke implementation logic through the proxy.

Additionally, the integrated Address library provides safe low-level call handling and contract verification. The system also supports initialization during deployment via encoded function calls, mimicking constructor behavior for upgradeable contracts.

Event emissions such as Upgraded and AdminChanged enhance transparency and traceability of administrative actions. The BEP20UpgradeableProxy serves as a lightweight wrapper tailored for BEP20 token implementations.

Overall, this design provides a secure, flexible, and maintainable framework for building upgradeable smart contract systems while preserving state and ensuring separation of concerns.

Executive Audit Summary

  • According to the standard audit assessment, the Customer`s solidity smart contracts are Secured”. Also, these contracts contain owner control, which does not make them fully decentralized.
  • We used various tools like Slither, Solhint and Remix IDE. At the same time this finding is based on critical analysis of the manual audit.
  • We found 0 critical, 0 high, 0 medium, 0 low, and 2 very low-level issues.

Audit Report in PDF


pdf

Audit Report Flip book

Please wait while flipbook is loading. For more related info, FAQs and issues please refer to DearFlip WordPress Flipbook Plugin Help documentation.

Leave a Reply

Your email address will not be published. Required fields are marked *

two × one =