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
It was same does not work both http / ws endpoint.
Backtrace
Plasma-evm run log
INFO [02-14|06:15:25.130] Deploying contracts for development mode
INFO [02-14|06:15:25.312] Deploy epoch handler contract hash=084d4a…86748b address=0x5ff3aFff10a4EfC1564f0B629B00a9BB6A9c29Ca
INFO [02-14|06:15:25.317] Wait until deploy transaction is mined
Fatal: Failed to deploy rootchain contract
Parity RPC trace log
2019-02-14 06:01:24 UTC TRACE rpc Request: {"jsonrpc":"2.0","id":8,"method":"eth_estimateGas","params" [{"data":"0x608060405234 ... , "from":"0xcd433f027339ad4f86b94463d1b0416a86dc3705","to":null,"value":"0x0"}
2019-02-14 06:01:24 UTC jsonrpc-eventloop-0 DEBUG rpc Response: {"jsonrpc":"2.0","error":{"code":-32016,"message":"The execution failed due to an exception."},"id":8}.
The text was updated successfully, but these errors were encountered:
Plasma-evm is communicating with rootchain node's event message.
So we should be careful, if makes compatible with parity.
One of the different thing between geth & parity
There is same error but different error message
geth: nonce too low
parity: nonce is too low
I think this issue also cause by something kind of this.
So @4000D, @thomasHin and I discussed about making compatible with parity, about a month ago.
Result was "Not for now", we are using go-ethereum as rootchain a while, not parity.
If
--dev
flag on, Plasma-evmrootchain
Deploy Process does not work via Parity node.There is worked well go-ethereum. @Jake-Song confirmed this.
System information
parity version: version Parity-Ethereum/v2.2.9-stable-5d5b372-20190203/x86_64-linux-gnu/rustc1.31.1
OS & Version: Ubuntu 16.04
Commit hash :
develop
commit b732d15Expected behaviour
RootChain
Contract deployed well.Actual behaviour
RootChain
Contract Deployed failed via plasma-evm dev mode.Steps to reproduce the behaviour
Modified
run.pls.sh
as like belowIt was same does not work both http / ws endpoint.
Backtrace
Plasma-evm run log
Parity RPC trace log
The text was updated successfully, but these errors were encountered: