-
Notifications
You must be signed in to change notification settings - Fork 346
Invalid opcode with byte code produced by solc v0.4.9 #526
Comments
@NodeGuy do you mean the actual "Invalid" Opcode and we don't account for it? |
Sorry, I hit |
That would likely be caused by the new opcode introduced by EIP 141 "designated invalid instruction": ethereum/EIPs#141 and indeed that is introduced as of solc 0.4.9 it is peculiar that the returned error does not return the actual opcode (that hex string is far too long); so that is a separate issue. |
Also facing same problem...did anyone resolve it?? |
I cannot reproduce this with solc 0.4.4, 0.4.9 or 0.4.20 - and I do not get the same payload as being sent their with transactAndHold. Will try with JS Libs |
closing this issue as outdated. feel free to reopen if it arises again. |
Please include in your bug report:
eris-db version
(docker image tag or branch if built from source)0.12.0
eris version
(if applicable)0.12.0
go version
(if applicable)go1.7.1 darwin/amd64
docker version
(if applicable)17.03.0-ce, build 60ccb22
Mac OS
I compiled the following contract with solc v0.4.9 and deployed it to Eris DB. I expected it to work without errors as it did when compiled by solc v0.3.4.
Check out https://github.com/eris-ltd/eris-contracts.js/tree/eris-db-%23526, run
npm install
, andTEST=record mocha test/HTTP
.The text was updated successfully, but these errors were encountered: