UNSUPPORTED_OPERATION getEnsAddress

[AlbertoDino]

Hi,
I just finished the course and started to play with zksync-101.

I've followed the tutorial and managed to compile and deploy the CrowdfundingCampaign contract to the zkSyncSepoliaTestnet network.

I've added to the project a new smart contract for playing around with tokens and openzeppelin.

here the code:

// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.0;

import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import "@openzeppelin/contracts/access/Ownable.sol";


contract MyDinoTokenAlpha is ERC20, Ownable {

    uint256 public constant MAX_SUPPLY = 100;

    constructor(address initialOwner) ERC20("Dino Token Alpha","DINOBA") Ownable() {
         _mint(msg.sender, MAX_SUPPLY); 
    }

    function mint(address to, uint256 amount) public onlyOwner {
        _mint(to, amount);
    }
}

it does compile, but if I try to deployed to zkSyncSepoliaTestnet I have this error

Error: network does not support ENS (operation="getEnsAddress", info={ "network": { "chainId": "300", "name": "unknown" } }, code=UNSUPPORTED_OPERATION, version=6.13.4)
    at makeError (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\utils\errors.ts:694:21)
    at assert (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\utils\errors.ts:715:25)
    at Function.getEnsAddress (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\ens-resolver.ts:545:15)
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Function.#getResolver (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\ens-resolver.ts:552:25)
    at async Function.fromName (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\ens-resolver.ts:590:26)
    at async Provider.getResolver (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\abstract-provider.ts:1193:16)
    at async Provider.resolveName (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\abstract-provider.ts:1203:26)
    at async Wallet.resolveName (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\providers\abstract-signer.ts:226:16)
    at async checkAddress (D:\repositories\blockchain\dinobzksync\zksync-101\node_modules\ethers\src.ts\address\checks.ts:60:20) {
  code: 'UNSUPPORTED_OPERATION',
  operation: 'getEnsAddress',
  info: { network: Network {} },
  shortMessage: 'network does not support ENS'
}

I could not find any useful information for this error .
Any idea why the the other contracts have not problem on being deployed but this token contract fail ?

Kind regards

Dino

[EngrPips]

Hey what version of Openzeppelin contract are you using so that I can try to reproduce this error.

[AlbertoDino]

Hi :),
with my latest attempt I've used the version that comes with zksync-101 template

"@openzeppelin/contracts": "^4.9.5",

But I've tried with the latest as well ^5.1.0 but I had the same error.

[EngrPips]

HHey @AlbertoDino, are you running this process on Remix or locally in your vcode with aid of a Foundry deployment script?

[AlbertoDino]

Sorry I haven't specified it.

Yes I'm running this on my local VSCode.

I used the zksync-101 template as a base and added a 5th script called 5-token with the token smart contract.

The deployment script is the same used by the other contracts deploy.ts.

I can see that is compiling and I got the artifacts generated correctly.

let me upload the code in a repo

[AlbertoDino]

code uploaded here https://github.com/AlbertoDino/zksync-dinotokenalpha

[EngrPips]

I wanted to mention that Foundry script doesn't work well with ZKSync but it seems like you are not explicitly using Foundry script for deployment.

[AlbertoDino]

I spent some time digging and recreated from scratch a project with Hardhat and @matterlabs/hardhat-zksync-deploy with latest versions .
Finally got my token smart contract deployed into ZKSync sepolia network .

I've updated the repo in case someone is looking for something similar :) .

Happy to close this discussion :) .

[EngrPips]

Awesome, Great job and thanks for sharing this with us.