You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a problem when I try to use this endpoint /api/v2/verifier/solidity/sources:verify-standard-json.
I have downloaded and run with docker, when I send a request, I get SUCCESS, but when I try to check the bytecode.
That is, the bytecodeType of my request is "DEPLOYED_BYTECODE". When I try to compare the data of localDeployedBytecodeParts with the bytecode received from the blockchain, they are not equal.
(I connected the two data values in localDeployedBytecodeParts), I tried to compare two bytecodes, how they differ, they differ in approximately 10 lines out of 160 lines.
But I also tried to verify the same contract address here https://t3.ftnscan.com/contract-verification, which I also use this service. In this way I can verify. In other words, in this case they are equal to each other, the only difference is that here I gave it input as json, and in my local I gave it as string.
The text was updated successfully, but these errors were encountered:
I have a problem when I try to use this endpoint /api/v2/verifier/solidity/sources:verify-standard-json.
I have downloaded and run with docker, when I send a request, I get SUCCESS, but when I try to check the bytecode.
That is, the bytecodeType of my request is "DEPLOYED_BYTECODE". When I try to compare the data of localDeployedBytecodeParts with the bytecode received from the blockchain, they are not equal.
(I connected the two data values in localDeployedBytecodeParts), I tried to compare two bytecodes, how they differ, they differ in approximately 10 lines out of 160 lines.
But I also tried to verify the same contract address here https://t3.ftnscan.com/contract-verification, which I also use this service. In this way I can verify. In other words, in this case they are equal to each other, the only difference is that here I gave it input as json, and in my local I gave it as string.
The text was updated successfully, but these errors were encountered: