1

I am doing PoC on Ethereum using Azure Ethereum network and Web3. I was working from last 1 month and I have created one smart contract for student management and that was working like fab. But for some reason I have deleted my Azure Ethereum network and created a new one. I have followed all the steps which I did previously, but its showing error in formal verification section like

Error: Type int256 not supported for state variable

The same smart contract code was working fine previously. Transactions are happening from Metamask but I cant read the data from functions so I am able to figure our where the exact issue is?

~pragma solidity ^0.4.9;
contract SimpleTest {
    int public count;

    function IncCounter()
    {
        count++;
    }

    function GetCounter() constant returns(int)
    {
        return count;
    }
}

I have searched for this issue but didn't find anything valuable, can someone please help me understand the exact issue and how to resolve it quickly.

  • Where does it show the error? What do you do to trigger the error? What steps are you following? – Mikko Ohtamaa Feb 15 '17 at 7:19
1

It sounds like a compiler error (I have no idea what is "formal verification section").

Most likely Solidity compiler has been upgraded to a newer version that comes with stricter checks.

However it is impossible to tell unless you include your contract source code and actual errors in the question. Please edit the question and use Markdown code formatting capabilities to add the necessary details.

  • i was edited post and added code which i was tried to use. today i am trying to run contract methods after 3/4 Days but still same issue is there – Sagar Feb 14 '17 at 11:33
  • I have resolved this using web method contract.new(). i have deployed smart contract from node js using web3 provider. – Sagar Feb 22 '17 at 8:42
1

Your contract code works fine: enter image description here

your variable count is public anyways. you can just try using the automatic getter SimpleTestInstance.count() my guess the problem you had was with uint and int. Remember that int or uint stands for uint256 and int256. So depending on the type signatures of your contracts, it may be wrong.

link to fiddle: https://ethfiddle.com/C6ARx6vyyo

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.