Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creation of OAR in ethereum-bridge #27

Closed
parunach opened this issue Jul 30, 2017 · 1 comment
Closed

Creation of OAR in ethereum-bridge #27

parunach opened this issue Jul 30, 2017 · 1 comment

Comments

@parunach
Copy link

I notice from multiple users about using

OAR = OraclizeAddrResolverI(resolve_addr); //add this line if you are using Oraclize in private chain environment

and to generate the resolve_addr

If you are currently using private chain, you need to use the Ethereum-Bridge API to generate a OAR, which is a log listener listens to the oraclize query from private chain and connect to oraclize serivice. The following list the steps of using Ethereum-Bridge:

  • Download the repository of Ethereum-Bridge by using git clone https://github.com/oraclize/ethereum-bridge, and execute npm install in the nodejs folder.
  • Unlock certain account (in this example we will use acoounts[0]) by using geth --unclock 0, and execute node plugin -H localhost:8545 -a 0. (make sure the account you unlock matches the account input to plugin.js)
  • Once you execute plugin.js, it will generate OAR for you to place in the constructor of your contract. After compiling it, you need to deploy it using any accounts except for the account you just unlocked.

I see that there is no plugin.js any more. All this must be outdated. How do I generate OAR to use with my private blockchain?

@marcogiglio
Copy link
Contributor

Hi @parunach, those instructions are outdated. Once started, the bridge automatically generates and deploys the OAR at a deterministic address. You don't need to add anything in your contract.

@parunach parunach closed this as completed Aug 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants