Error code 32603 on remix and metamask

Support Contracts
1

Hello, I am super newbie here trying smart contracts for the first time, using remix with metamask connected in my browser (on BSC testnet). I found this simple code and deployed it, everything worked and the contract is deployed, I also imported this test token symbol into my metamask using contract address

pragma solidity ^0.8.2;
import "@openzeppelin/contracts/token/ERC20/ERC20.sol";
contract WW is ERC20 {
    constructor(uint256 initialSupply) ERC20("WW coin test", "WW") {
        _mint(msg.sender, initialSupply);
    }
}

Then I went to openzeppelin wizard and created this simple code, simple enough that there cannot be really any bug in the code but I cannot deploy it, I am getting code 32603 with "Internal Server Error" message from Metamask. What am I doing wrong? My metamask seem to be workign correctly, I have a TBNB balance obtained in test faucet etc. I searched google extensively, a few people have this error code 32603 but no real solution

pragma solidity ^0.8.2;

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

contract WW2Test is ERC20, Ownable {
    constructor() ERC20("WW2 test", "WW2") {
        _mint(msg.sender, 100 * 10 ** decimals());
    }

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

why is my post getting 0 replies? :slight_smile: Surely someone must know the answer

3

Hey @kura,

I just tried to deploy the contract you're showing and it all works well.

For context, these errors come from the JSON RPC provider, which may vary depending on the node they're using (I guess BNB has the same implementation across nodes), and whatever setup is used by the providers for client management (eg. rate limiting or similar). I'm afraid 32603 and Internal Server Error could be a generic default error and that'd explain different answers on internet.

My best advice in these cases is to change the JSON PRC provider and/or try a different deployment method on a Hardhat/Foundry environment so it doesn't go through Metamask. You can download the Hardhat version from the wizard.

A good place for getting alternative JSON RPCs could be https://chainlist.org

Best