Yesterday I deployed a contract to Ropsten (https://ropsten.etherscan.io/address/0x1fe59c223fa4e9781237f0f49a15ca598069cc30) that relies on V2 of the ABI encoder. Thus it includes statement
pragma experimental ABIEncoderV2;
I tried to run Etherscan's code verification (https://ropsten.etherscan.io/verifyContract2) with a flattened version of my Solidity code, matching compiler version, optimization flag, optimizer runs etc. The code verification result, however, is negative.
Back in June when I also deployed contracts with the same pragma I got message from Etherscan helpdesk that they don't support ABIEncoderV2. This despite the fact that compilation at Remix only issues a warning and Etherscan claims to support contracts that compile at Remix.
So I am looking for alternatives. Can anyone lend support to the hypothesis that it is lack of support for ABIEncoderV2 that is still causing code verification problems? Also are there other alternatives for public code verification of smart contracts?