What does this do? about ethereum-bridge

[bertani]

Hello @maurelian, the reason why we have chosen not to write any extensive tutorial/documentation on the ethereum-bridge tool, is that this is still highly experimental and subject to breaking changes (as specified in the README).
Specifically, we have plans to change a lot the way you would interact with this tool in the coming weeks so please be patient for some more weeks until we roll this out :)

All your questions are around the internal workings of the Oraclize contracts and architecture so its understanding is of limited utility given its wiring-only use. Most of your questions can find an answer by reading our public Ethereum contracts code here.

• when you call oraclize_query, the connector is called and the Oraclize engine starts computing the relevant answer - which is then sent back to the calling contract
• the callback address is the address Oraclize uses to send back data to the calling contracts
• the connector is where you find most of the Oraclize onchain logic, it is the gateway to our offchain engine

I hope this helps.

[maurelian]

Thanks very much for the response. I appreciate it and understand this is a young tool!

the callback address is the address Oraclize uses to send back data to the calling contracts

But my callback address is a non-contract account.

So you're sending msg.data to a non-contract account? That's not something I'd considered as useful previously. There would be no logs generated. Is bridge then reading some data from the transaction receipt?

[bertani]

I am not sure I understand your question.

The callback is the transaction Oraclize sends back to the calling contract. Let's say your contract A calls out to Oraclize via oraclize_query. Oraclize will send back the result with a new transaction (the callback one), sent from a given Oraclize account (the callback address) to the calling contract (A).

Does that make sense to you?