nikitosing

@vbaranov cannot reproduce the issue This is requested url: `https://blockscout.com/xdai/mainnet/smart-contracts/0x93d0c9a35c43f6BC999416A06aaDF21E68B29EBA?function_name=balanceOf&method_id=00fdd58e&type=regular&args_count=2&arg_1=873&arg_0=0x343aa9b908bf6ef8d0e954221789881750c9c3ce` (now args format is different unlike attached log)

@vbaranov Is the issue still actual?

@akshar How did you compose json file? Did you include all sources in json/flattened source code?

@akshar could you please try to repeat verification after applying [this commit](https://github.com/blockscout/blockscout/commit/cb61231b42bef2d7b95d9d4a29bbc94f8753f8c4). Or just use master branch

@akshar the name should match with deployed contract's name at address. BlockScout is verifying such proxies without any diffculties. On Gnosis Chain you could find examples by `UUPSProxy` name: https://blockscout.com/xdai/mainnet/address/0x2dFe937cD98Ab92e59cF3139138f18c823a4efE7/contracts

@akshar Could you send link to contract sources + compiler params? And if it's possible link to unverified contract

@akshar what is the status? Did new update of smart-contract verifier microservice help and we can close the issue or no?

@akshar Is it your instance? Please take a look https://github.com/blockscout/blockscout/issues/6264#issuecomment-1280605349

@ss75710541 > block hash 0xda59513ac324b7abec59f992260087bb65d82bbe14cb752672979635290a19f6 It's an intermediate state. It has now been removed What do you mean by removing? What did remove it?

@jjhesk Did you set ENV variables? I think the problem in empty `DATABASE_URL` variable