I can work with oraclize only using a private chain created with testrpc. If I try to use the ethereum-bridge over my locally created private chain it doesn't answer, nether I get message in the ethereum-bridge console.

Actually is it a supported feature or is it only possible to work with private chain created with testrpc?

  • Can you elaborate on the steps you have taken? Did you deploy the bridge in your private chain in active or broadcast mode? Are youusing a deterministic OAR? Apr 28, 2018 at 2:55
  • Step to reproduce: On TestRpc -Run the TestRpc. -Download ethereum-bridge; -Install ethereum bridge in his folder; -Run the ethereum bridge with the following command (Active mode): ` node bridge -H localhost:8545 -a 1 ` -Deploy the using_oraclize contract; -Deploy the TestOraclizeCall contract; I'm not using deterministic OAR and I'm uploading the calling contract with the right OAR that the ethereum-bridge console give to me. This process works on test rpc. Hovewer, Following the same steps in the private chain (Obviosly chaging the connecting port) is not working. May 3, 2018 at 10:23

1 Answer 1


The answer is yes! you can use the ethereum-bridge over your locally private chain created by geth or parity,but only on dev-modechain!

After 3 days and a day morning and thanks to the help from @D-Nice @gskapka , I finally solved the problem.I need to put my thoughts together to help guys who may encounter the same problem. - only support the dev geth private network I am sorry to say that the oraclize(ethereum-bridge) is only supported the devchain , which means you should start your private network using geth like

geth --networkid 15 --datadir ./data --rpc --rpcapi "admin,debug,eth,miner,net,personal,txpool,web3" --rpcport "8545" --rpccorsdomain "*"  --dev

or simply, you can start you your private network using

geth --dev --rpc console
  • if you deploy the contract using ethereum-bridge on Non-dev private network, you will get gas error like
gas required exceeds allowance or always failing transaction in private network

so, all the problem is caused by Non-devprivate network! Good luck for you!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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