CryptoCoinsInfoClub.com

Ethereum Bridge

The Api Bridge To The Ethereum Testnet Is Nowthere

The Api Bridge To The Ethereum Testnet Is Nowthere

The API bridge to the Ethereum testnet is nowthere Playing around on Ethereum comes at a cost while designing your brand new smart contract your time is not the only resource you are spending, but gas costs come in as well. Other than this, bloating the mainchain with your temporary tests is not something anyone would encourage you to do. This is why developers are mostly testing their Ethereum code on their private chains or on public testnets. Morden is exactly that. Getting on track with it is as easy as typing geth testnet and you can get some free testnet coins from faucets . Being Oraclize a bridge between smart contracts and the Internet, one piece of our engine is sitting on the connected chain itself as a smart contract. This means that if you want to test your Oraclize integration, this has had to be done on the Ethereum mainchain which could be sort of annoying (other than expensive!). Oraclize can be easily plug in, on our side, with any chain, both public and private. What we are announcing today is the integration with both Morden (public testnet with networkID 2) and the test.ether.camp / ConsenSys one (public testnet with networkID 161). This means that you can test Oraclize on testnets for free (well, paying testnet coins). The way it works is exactly the same as before, the only thing you need to change in your smart contract code is a one-time call to the function oraclize_setNetwork, which is as easy as typing in your constructor code (or wherever you find more appropriate) oraclize_setNetwork(networkID_testNet). Our Solidity API on github has been updated accordingly feel free to join our gitter channel if you need any support while poking around with our toolset ! Happy new year and happy coding to all you brave developers Continue reading >>

Dogecoin (doge) Core Developers Distance Themselves From The Upcoming Dogethereum (dogx) Hark Fork

Dogecoin (doge) Core Developers Distance Themselves From The Upcoming Dogethereum (dogx) Hark Fork

Dogecoin (DOGE) Core Developers Distance Themselves from the Upcoming Dogethereum (DOGX) Hark Fork There are many people, cryptocurrency investors alike that still consider Dogecoin (DOGE) a joke at least according to the New York Times report published late 2017. Although the publication that described Dogecoin as a half-baked Bitcoin copy that was developed to dupe gullible people has already been amended; the damaged caused by the misinformation is yet to be repaired. However, Dogecoin seems to be to do fine all the same. One of the four Dogecoin founders, Ross Nicoll, has spent time clearing the myths that were popularised by the New York Times publication. In fact aside from the infamous myths, Dogecoin is in the middle of a project dubbed Doge-Ethereum bridge project. This ongoing development will allow Dogecoin to ride on Ethereum in order for it to be utilized in smart contracts. The project is testing the Ethereum network and is seen as a turning point for DOGE. It will elevate Dogecoin to the standards traders and merchants across the crypto world would like to see. Besides, the Dogethereum Bridge will tremendously scale up Dogecoin transactions improving usability. Nicoll goes ahead to dispel the negative rumours stating that Dogecoin like any other cryptocurrencies undergoes updates, occasional releases as well us usability which is commonly stress tested. On the contrary, Dogecoin (DOGE) is coming up as one of the most used cryptocurrencies in payments. Similarly, it is among the top ten used coins for sending payments. A quote from one of Nicolls interviews reads, We are very very careful with everything we do. Were taking code that is well tested keeping half a billion dollars of peoples money over four years stable. . . Were doing very very very well, T Continue reading >>

Github - Johnhckuo/oraclize-tutorial: Some Basic Introductions For A Useful Oracle Service

Github - Johnhckuo/oraclize-tutorial: Some Basic Introductions For A Useful Oracle Service

Some basic introductions for a useful oracle service Oracle service build the bridge between blockchain and the real world, and the following image describes the underlying mechanism of the Oraclize . It uses the TLSNotary to make its serivce trust-worthy, and pre-fetch the real world data for all the nodes within the network to achieve consensus, which cannot be easiliy done without oracle serivce. The following example shows a simple contract using the orcalize serivce //this import should be replaced by oraclizeAPI.solimport "dev.oraclize.it/api.sol";contract YoutubeViews is usingOraclize { uint public viewsCount; function YoutubeViews() { //OAR = OraclizeAddrResolverI(resolve_addr); //add this line if you are using Oraclize in private chain environment update(0); } function __callback(bytes32 myid, string result) { if (msg.sender != oraclize_cbAddress()) throw; viewsCount = parseInt(result, 0); // do something with viewsCount update(60*10); // update viewsCount every 10 minutes } function update(uint delay) { oraclize_query(delay, 'URL', 'html("watch-view-count")]/text())'); }} The example shows three steps to utilize the oraclize service: Constructor will first call the update function, which will trigger the orclize_query transaction and commence data fetching process. You also have to specify the delay (in seconds) from the current time or the timestamp in the future as first argument. Once the data query returns the result, it will call the __callback function with the result passed into the function. We can now do some operation using the code defined in __callback function, and you can also call update function again if you want to execute the query once in a while. Caution! Please note that in order for the future timestamp to be accepted by Oraclize it must Continue reading >>

Oraclize Documentation

Oraclize Documentation

Welcome to the Documentation of Oraclize! The documentation is divided in the following sections: Background : the rationale behind the Oraclizes Oracle Model General Concepts : the main concepts behind Oraclize Data-Sources : information regarding the types of data sources Oraclize supports Integrations : how to integrate a blockchain application with Oraclize Development Tools : a list of tools to aide development of Oraclize-integrated smart contracts Security Deep Dive : how Oraclizes Authenticity proofs works Pricing : information on our pricing model for production uses Oraclize is the leading oracle service for smart contracts and blockchain applications, serving thousands of requests for day every day on Ethereum, Bitcoin and Rootstock. In the blockchain space, an oracle is a party which provides data. The need for such figure arise from the fact that blockchain applications, such as Bitcoin scripts and smart contracts cannot access and fetch directly the data they require: price feeds for assets and financial applications; weather-related informations for peer-to-peer insurance; random number generation for gambling. But to rely on a new trusted intermediary, the oracle in this case, it would be betraying the security and reduced-trust model of blockchain applications: which is what makes them interesting and useful in first place. One solution is to accept data inputs from more than one untrusted or partially trusted party and then execute the data-dependent action only after a number of them have provided the same answer or an answer within some constrains. This type of system can be considered a decentralized oracle system. Unfortunately, this approach has severe limitations: It requires a predefined standard on data format It is inherently inefficient: all Continue reading >>

Parity Bridge Parity Ethereum Documentation

Parity Bridge Parity Ethereum Documentation

this guide assumes that you are one of the authorities ofa PoA chain foreign and want to use the bridge to connectforeign to another chain home.this will create an ERC20 token on foreign that is backed byether on home. since all bridge authorities use the same contracts on foreign and homeone authority has to go ahead and deploy them. if the process is done correctly the other non-deploying authorities dont have to trustthe deploying authority. upfront you must know the addresses of all authorities (authorities)es well as the number of required_signatures initial deployment steps for any authority (deploying and non-deploying) assuming you are authority with authority_address. install parity.we tested it with parity 1.8.10 though it should work with the latest stable release. start a parity node that connects to home chain, has authority_address unlockedand ipc enabled at home.ipc. TODO add instructions. please refer tothe parity documentation for now. start a parity node that connects to foreign chain, has authority_address unlockedand ipc enabled at foreign.ipc. TODO add instructions. please refer tothe parity documentation for now. copy integration-tests/bridge_config.toml to a local bridge_config.toml. within bridge_config.toml resolve/fill-in all the ACTION REQUIREDs. further deployment steps for deploying authority env RUST_LOG=info bridge --config bridge_config.toml --database bridge.db it should eventually print something like this: INFO:bridge: Deployed new bridge contractsINFO:bridge:home_contract_address = "0xebd3944af37ccc6b67ff61239ac4fef229c8f69f"foreign_contract_address = "0xebd3944af37ccc6b67ff61239ac4fef229c8f69f"home_deploy = 1foreign_deploy = 1checked_deposit_relay = 1checked_withdraw_relay = 1checked_withdraw_confirm = 1 congratulations! the bridge Continue reading >>

Doge Is Helping Ethereum Solve Its Biggest Issue

Doge Is Helping Ethereum Solve Its Biggest Issue

Doge Is Helping Ethereum Solve Its Biggest Issue Feb 18, 2018 at 10:00 UTC |UpdatedFeb 20, 2018 at 09:09 UTC A cryptocurrency modeled after a dog meme is proving yet again it's not just a joke. Created on a whim in 2013, dogecoin isn't simply still around , it's playing a crucial role in the ongoing testing of at least one "serious" technology. In fact, on February 5, it notably factored into an experiment that successfully showcased one of ethereum's more enterprising projects. On that date, the much-anticipated technology truebit successfully sent dogecoin to ethereum's Rinkeby testnet, where it became a distinct asset on that blockchain. A historic first, the transaction marked the completion of a years-long project developers see as a stepping stone toward the interoperability of crypto assets more broadly. Nicknamed the "dogethereum bridge," the test also marks the first real release for truebit, which aims to solve one of ethereum's biggest problems: scalability. In short, the smart contract platform can't support many users right now. Indeed, because of all the data ethereum needs to store in its globally distributed database, it requires more than three times as much data as bitcoin, and that's making it more difficult for users to run. Though truebitis lesser-known than scaling solutions like raiden and sharding, the technology is perhaps more ambitious because it's designed to scale any type of ethereum computation, rather than just transactions. This is key, since ethereum bills itself as more than "just" a financial cryptocurrency. In the long run, truebit wants to scale video, machine learning or just about any computation you can think of, and dogethereum is the first use case, so far. "We built a first version of that, which we're calling 'truebit lite.' Continue reading >>

The Technicals Of Interoperabilityintroducing The Ethereum Pegzone

The Technicals Of Interoperabilityintroducing The Ethereum Pegzone

Research/writing, blockchain tech. Mostly Bitcoin & @cosmos. Comms @Tendermint_team. Passion for subversion. Ex @NASAJPL The Technicals of InteroperabilityIntroducing the Ethereum PegZone Cross-blockchain crypto-asset transfer is core of what we do at Cosmos. Within the ecosystem, crypto-assets are transferred via the IBC protocol, an Inter-Blockchain Communication protocol , which facilitates interoperability. Notably, IBC only works if both the starting and the destination chains have settlement finality. Fortunately or unfortunately, neither Bitcoin nor Ethereum have finality guarantees; rather, they have probabilistic finality. [Edit: for now Ethereum doesnt benefit from the property of finality; until, that is, Casper the Friendly Finality Gadget (FFG) is implemented in the near-term future.] What this means is, the deeper down the chain a block is, the less likely the chain its on will get reorganized, giving you a high level of confidence that the block is final. But because probabilistic guarantees do not protect against reorgs, transferring assets securely across chains via IBC is impossible. This prompts the question: How can Cosmos zones interoperate with pre-existing blockchains absent finality? Peg zones are our solution. A peg zone is an account-based blockchain which bridges zones within Cosmos to external chains like Bitcoin or Ethereum. It acts as an adaptor zone or a finality gadget, in Casper-speak which translates finality for probabilistically finalized blockchains by imposing a finality threshold at some arbitrary number of blocks to achieve pseudo-finality. Generally, this translator zone design can be classified as a 2-way peg (2WP). Consensus engines such as Tendermint Core offer settlement finality. To better understand how it works, please re Continue reading >>

Komodo Bridges The Gap Between Bitcoin And Ethereum

Komodo Bridges The Gap Between Bitcoin And Ethereum

Komodo Bridges the Gap Between Bitcoin and Ethereum Komodo is the world leader in atomic swaps and we are proud to announce that we have performed an etomic swap by swapping between Ethereum and Dogecoin! An etomic swap is like an atomic swap however it swaps an Ethereum/ERC20 token for any other coin. This is a groundbreaking development because it means we have succeeded in bridging the gap between the worlds two largest and most popular blockchains Bitcoin and Ethereum. In the past, cross-chain atomic swaps between tokens tied to the Ethereum blockchain (ETH/ERC20 tokens) and coins created using the Bitcoin codebase were not thought possible. For instance, if Alice had DOGE that she wanted to trade for an ERC20 token, she would have had to trade Doge->Bitcoin->Ethereum->ERC20. This would make the transaction extremely costly, as each trade made on a centralized exchange comes with a transaction fee. This is also extremely time inefficient. With Komodos atomic swap technology, Alice is now able to trade directly with another individual who holds any ERC20 token. For example, if Alice wants to trade DOGE for an ERC20 she can connect with Bob who wants to trade ERC20 for DOGE and the trade will be executed in a totally decentralised way. The decentralized, peer-to-peer nature of this transaction makes it cheaper, trustless and extremely secure. How did we make this etomic swap possible? We completed this swap using BarterDEX , Komodos decentralized exchange, which allows users to exchange any cryptocurrency that has been linked to BarterDEX through optimally secure, peer-to-peer transactions. At present, BarterDEX features 100+ coins and will grow to support 1000+ cryptocurrencies once we fully integrate the ERC20 tokens into the DEX. Furthermore, this recent achieveme Continue reading >>

Episode 3: The Doge-ethereum Bridge With Guest Harley Swick - Doge Radio (podcast)

Episode 3: The Doge-ethereum Bridge With Guest Harley Swick - Doge Radio (podcast)

Episode 3: The Doge-Ethereum bridge with guest Harley Swick MP3 • Episode home • Series home • Public Feed ByJohnny Renton.Discovered by Player FM and our community copyright is owned by the publisher, not Player FM, and audio streamed directly from their servers. In this episode we chat with Harley Swick, a developer involved with the Doge-Ethereum bridge project. Learn all about what the project is about, and a bit more about one of the developers behind it! 3 episodes available.A new episode about every14 daysaveraging 48 mins duration. In this episode we chat with Harley Swick, a developer involved with the Doge-Ethereum bridge project. Learn all about what the project is about, and a bit more about one of the developers behind it! Episode Notes: Coming soon! The episode in which we discuss Jackson Palmer causing a stir, Year of the Doge video contest winners, fake ICO's, buying and using Dogecoin, and the Venezuelan Petro. Follow us on Twitter @muchdogeradio, myself @mrjohnnyrenton, and soon to be coming to YouTube. You can find our episodes on iTunes and on Stitcher. Show notes: Jackson Palmer's t ... In the premier episode of Doge Radio we talk about who we are, and what brought us to Dogecoin. We muse about the current state of Dogecoin and crypto, and discuss The Year of the Doge video contest. What if radio played only the shows you care about, when you want? Player FM is scanning the web for high-quality podcast content right now. Try us out on any web browser desktop, mobile, or tablet. Start listening to Doge Radio on your phone today with Player FM's free Android app. You can sync with your account with this website too. Guides you to smart, interesting podcasts based on category, channel, or even specific topics Right from the start, Continue reading >>

Bridging The App Scaling Now With Parity Bridge

Bridging The App Scaling Now With Parity Bridge

Bridging the App Scaling now with Parity Bridge Transaction fees on the Ethereum main network have risen to rates that are far too expensive for Apps to run efficiently. Decentralised initiatives such as Giveth and Swarm.City have seen their projects hampered by high gas costs, forcing them to look for alternative ways to securely run their Apps. We realised at Parity Technologies that we can already mitigate scaling issues using one of the core components of Polkadot . This is why we are excited to announce the initial test deployment of Parity Bridge , a solution for connecting fast and cheap Proof of Authority (PoA) chains with the Ethereum public network and any other Ethereum-like Proof-of-Work chain. This way, developers can start testing this short-term scaling solution to reduce the cost of running Apps on blockchains. The first phase of Parity Bridge uses the Ropsten testnet to act as the main network, or Home bridge, until community developers have tested it enough to ensure a secure and efficient link between two EVM-based chains. First, a user deposits Ether from the mainnet to the Home bridge contract, then the App runs on Kovan for as long as required, then finally, the user withdraws their Ether back on the mainnet. Rather than paying for gas on every transaction on the mainnet, users pay only the gas for two transactions the deposit and the withdrawal. To illustrate lets give an example of how the bridge could save Swarm.City and its users gas costs. Swarm.City has tokens on mainnet and a App they want to deploy soon. By design, the tokens will be in constant use in the App, which now makes deploying to mainnet too expensive. By deploying their App to another chain such as Kovan, Swarm.City users could more freely use the network since gas prices are ne Continue reading >>

Contract Debugging - Oracle (oraclize.it) With Truffle And Testrpc - Ethereum Stack Exchange

Contract Debugging - Oracle (oraclize.it) With Truffle And Testrpc - Ethereum Stack Exchange

Oracle (oraclize.it) with Truffle and Testrpc As I understood in the blockchain, it is "not" possible to interact with webservices outside the blockchain. This must be done over oracles in order to verfiy that the request is secure, and the state change can be done in the blockchain. Please correct me, if I am wrong. I am currently working with Testrpc, Truffle, and React in order to test my smart contract. Now I want to integrate oraclize.it into my environment. What is the best way to do this? I tried to copy the testexamples into my Contract folder, but in the contract there is this reference: import "github.com/oraclize/ethereum-api/oraclizeAPI.sol"; How can I integrate this reference to my folder structure? I tried to copy the following files to my contract folder: What's the best way to implement Oraclize with Truffle and Testrpc/Ganache? It is very possible to use the Oraclize service with testrpc alongside truffle. Firstly, you need to follow the naming convention of contract filenames in truffle. As per their docs: Truffle expects your contract files to define contracts that match their filenames exactly Therefore you should download the Oraclize API from the Oraclize github repo, here's a specific link to the file oraclizeAPI_0.4.sol . Download this to the truffle contracts folder of your working directory, and rename the file to usingOraclize.sol. This is required so at compilation time, truffle knows which specific contract to compile from within the file. The other alternative is to directly paste all of the API into the required contract, but adding and renaming the API itself is likely the most elegant solution I'm aware of at the moment. Now you will be able to import the API on your other contracts within that folder by including import "usingOraclize. Continue reading >>

Blockchain - How Is It Possible For Ethereum-bridge To Deploy A Contract At A Deterministic Address? - Ethereum Stack Exchange

Blockchain - How Is It Possible For Ethereum-bridge To Deploy A Contract At A Deterministic Address? - Ethereum Stack Exchange

How is it possible for ethereum-bridge to deploy a contract at a deterministic address? Here I provide a snippet of the output generated by ethereum-bridge on startup: [2017-10-13T07:25:55.920Z] INFO deploying the oraclize connector contract...[2017-10-13T07:26:16.357Z] INFO connector deployed to: 0x3ae9795a5c4ef9f803d56437163b3abd39649525[2017-10-13T07:26:16.482Z] INFO deploying the address resolver with a deterministic address...[2017-10-13T07:26:47.730Z] INFO address resolver (OAR) deployed to: 0x6f485c8bf6fc43ea212e93bbf8ce046c7f1cb475 Indeed, the address of the OAR contract is always 0x6f485c8bf6fc43ea212e93bbf8ce046c7f1cb475, but as the contract's address is determined by hashing the sender's account + nonce, how can Oraclize (ethereum-bridge) always deploy to the same address? The trick is very simple, they use the same account and only with nonce = 0. From their github repo // used only to deploy a deterministic address resolver (OAR) (contract address = sha3(rlp.encode([normalize_address(sender), nonce]))[12:])const OAR_ONLY_PRIV_KEY = Buffer.from('79a98ade62c92444178d73409fbce37a360b36a2483dda666d26270c8a50f5c7', 'hex')const OAR_ONLY_ADDRESS = '0x935A0F8F4B8752C61f00D1f67b67685665ff8Cf6' In the same file bridge-account.js they have the following functions BridgeAccount.prototype.getTempAddress = function () { return OAR_ONLY_ADDRESS}BridgeAccount.prototype.getTempPrivKey = function () { return OAR_ONLY_PRIV_KEY} In the function deployOAR in bridge-core.js they have the following BridgeTxManager().sendRawTx({ 'from': self.account, 'data': oraclizeAddressResolverBin, 'gas': 324702, '$temporary_account': true}, function (err, contract) { The important part is '$temporary_account': true Now looking at sendRawTx in bridge-tx-manager.js we have BlockchainInterface( Continue reading >>

The Inside Woof On The Dog-eth (doge, Xdg, Eth) Bridge Contract: Its Not A New Coin

The Inside Woof On The Dog-eth (doge, Xdg, Eth) Bridge Contract: Its Not A New Coin

The Inside Woof on the Dog-Eth (DOGE, XDG, ETH) Bridge Contract: Its Not a New Coin Facebook Twitter Google+ LinkedIn Reddit WhatsApp Telegram Share via Email Photo credit: Pinguino Kolb at pinguinokolb.com In an exclusive Twitter exchange, Ross Nicoll, of the Dogecoin Development Team, explained that what he and a team of cryptocurrency architects are working on is not a coin, but a new application for DOGE and ETH that is paving the way for one cryptocurrency to interact with another. The news of these Dog-Eth bridge contracts, however, has brought with it a copy-cat project that seems to be taking advantage of the publicity that the news of the Dog-Eth bridge contracts have found. Nichol warns the cryptocurrency community that the Dogethereum coin is not related to the Dog-Eth bridge contract project that he is involved with. Apparently someone's marketing a Dogethereum cryptocurrency. Obviously anyone's free to launch whatever they like, but please be careful with anything that can't be converted directly back to Dogecoin. What we're involved in is a locked 1:1 Doge/Doge-on-ether currency, explained Nicoll, known as the chatty Dogecoin developer. In a recorded demonstration of the Dog-Eth bridge that's available on YouTube , Ross and a team of cryptocurrency architects that are working on the project demonstrated the process. They recorded the live transmission of Doge into an Ethereum network in front of a team of other crytpocurrency architects who served as judges for the transaction. On hand was X, the other half of the Dogecoin development team, as well as Hudson Jameson from the Ethereum Foundation, and the team of architects from Truebit, who are handling the computational scalability part of the project, which is complex. This project is significant, Nicoll Continue reading >>

Enter The Rabbit Hole: The Doge-ethereum Artproject

Enter The Rabbit Hole: The Doge-ethereum Artproject

Enter the Rabbit Hole: The Doge-Ethereum ArtProject The Doge-Ethereum art project at ETHDenver. Two years ago, a handful of anonymous crypto hodlers funded a bounty for the development of the Doge-Ethereum bridge. Truebit recently won part of this bounty. The Doge-Ethereum bridge allows one to move coins between the Doge and Ethereum blockchains. You send a transaction on the Dogecoin blockchain forfeiting control of your coins, and an Ethereum contract mints you an equal number of EthDoge (or should I say WOW) ERC20 tokens. You can then use these tokens within the ethereum ecosystem send them to smart contracts, trade them on decentralized exchanges, or use them to buy cryptokitties. At any point, a WOW token holder can burn their tokens and receive Dogecoins back on the Doge chain. This completes the bridge. To get into the history of the bridge and why it matters, refer to this tweetstorm from Alex van de Sande: The sticking point, and the reason why the bridge hadnt been built so far, is that the Ethereum relay needs to verify Dogecoins Proof-of-Work. Scrypt is a memory-hard and computationally intensive function, and cannot be computed within the Ethereum block gas limit. The community has been playing with different solutions for years you can see Vitaliks 2015 solution of splitting Scrypt into multiple transactions here . The problem eventually drew the attention of Christian Reitwiessner and Jason Teutsch and was a good proof of concept for Truebit. One would run Scrypt off-chain and verify it using Truebits interactive protocol. We recently demoed this system on the Rinkeby testnet. Truebit verification for Scrypt on the Rinkeby testnet We were awarded 25% of the bounty for the progress shown in the demo. We shared this with our collaborators Oscar Guinzberg a Continue reading >>

Github - Oraclize/ethereum-bridge: Independent Bridge To Link Any Ethereum Network With The Oraclize Engine

Github - Oraclize/ethereum-bridge: Independent Bridge To Link Any Ethereum Network With The Oraclize Engine

Independent bridge to link any Ethereum network with the Oraclize engine If nothing happens, download GitHub Desktop and try again. If nothing happens, download GitHub Desktop and try again. If nothing happens, download Xcode and try again. If nothing happens, download the GitHub extension for Visual Studio and try again. This tool enables any non-public blockchain instance to interact with the Oraclize service. Please note that at this point this tool is still experimental and subject to change without notice. run sudo apt-get install build-essential -y You should run the following commands from within the ethereum-bridge folder. active mode (deploy and query contracts using one account on your main node) [DEFAULT] broadcast mode (deploy and query contracts using a local account (the node will be used only to broadcast the txs)) After you have correctly deployed the address resolver and the connector on your blockchain you can load the previous instance using the --oar flag (with the latest oar address generated) or using --instance latest if you are not using the deterministic OAR you also need to update your contract constructor with the new address resolver generated (deploy contracts using the account 1 found on the localhost:8545 node) node bridge -H localhost:8545 --broadcast --new (generate a new address locally and deploy contracts (txs broadcasted to localhost:8545 node)) or if you already have one or more account in your keys.json file: node bridge -H localhost:8545 --broadcast -a 0 (load the first account in your keys.json file (index n.0) and deploy contracts (txs broadcasted to localhost:8545 node)) Add OAR = OraclizeAddrResolverI(EnterYourOarCustomAddress); to your contract constructor, example: Where EnterYourOarCustomAddress is the address resolver gen Continue reading >>

More in ethereum