(Closed)Has anyone deployed an Upgradeable Contract?

Fuzz — Sun, 18 Dec 2022 22:17:21 +0000

Hi,

I'm using the OpenZeppelin base contracts with their transparent proxy feature.

The deployment of the proxy is successful but when it comes to verification on the explorer the verification fails.

Without using the upgradeable proxy, the contract can be successfully verified. Does anyone have any experience with upgradeable contracts using OpenZeppelin?

Thank you.

Debugging & Solving Hardhat Flattening Issues

Fuzz — Sun, 18 Dec 2022 19:55:54 +0000

Hello!

I've discovered a few tricks to validate contracts, built and flattened by Hardhat, on the XDC blockchain explorer.

TL;DR

Don't turn on the XDC Explorer's optimization flag.
Remove the config: {...} preamble in the flattened file.
In the flattened file, replace all SPDX-License-Identifiers with SPDX-License-Identifier-FLATTEN-SUPPRESS-WARNING

How it started ...

This is a brief description of a problem I ran into this week while using Hardhat version 2.12.4 with solc 0.8.17 and the current version of the XDC Explorer (for both Apothem and Mainnet).

I've been developing an XRC20 compliant Token using Open Zeppelin's contracts with several of the supporting interfaces such as ERC20Burnable and Pausable. The contract was compiled with the optimizer enabled and set to 200 runs.

Deploying the contract to Apothem went smoothly. I then flattened the contract using a technique that's been documented in the XDC docs:

hardhat flatten ./contracts/FuzzTest.sol > ./contracts-flattened/FuzzTest.sol

... and then attempted to verify the contract on the Apothem Explorer. Every approach I tried failed either with an immediate non-descriptive error or a timeout (HTTP 524)!

The Quest ...

After a very useful conversation on the XDC Discord (thanks @menezesphill !) I went back to basics and setup the contract in Remix using this guide.

I diff'd the output of the Flattener Remix plugin and through a process of experimentation I discovered three key steps for solving this issue.

The Answer

1. Hardhat's config preamble needs to be removed

Hardhat emits this in the flattened file and it's not recognised by the XDC Explorer - it needs to be deleted before being uploaded:

config:
{"solidity":{"version":"0.8.17","settings":{"optimizer":{"enabled":true,"runs":200}}},"networks":{"xinfin":{"url":"https://erpc.apothem.network","accounts":["xxx"]}}}

2. `SPDX-License-Identifiers` have to be replaced

Replace SPDX-License-Identifiers with SPDX-License-Identifier-FLATTEN-SUPPRESS-WARNING

3. XDC Explorer's Optimizer Flag

When uploading your flattened file, do not enable the Optimization flag.

That's it! Hope you find this post useful. Happy holidays and merry coding!

Developers Forum for XinFin XDC Network: Fuzz