If you want to dive deeper, here there are more details, but in order to use them you don t need to specify anything really, they resolve automatically https://github.com/provable-things/ethereum-api/blob/9f34daaa550202c44f48cdee7754245074bde65d/oraclizeAPI_0.4.25.sol#L324
or does oraclize just not send the tx
@bonedaddy it is technically impossible to have 100% guarantee that the tx will fail before sending it onchain as the receiving contract may depend on the chain state which evolves over time and whose ultimate judges are miners, hence we always send it onchain regardless of the offchain "simulation" of the tx execution
For instance you can use provable_setCustomGasPrice(4000000000);
Yes, when I tested on the mainnet, it hasn’t arrived yet. I thought you would choose the average gasprice by default for the callback.
Yes, this is reasonable, I just make sure what I will do next
Hi support, if we were to compile ngrok or localtunnel service in the docker machine spawned by the t2.micro instance could this achieve a static callback IP?
Hi @bonedaddy - the
__callback is entirely under your control, since you write that function in your smart contract. The Provable service merely calls it with the string result of your query, and the queryId. As for why yours are failing, do you happen to have a query ID of one of your calls? There is no throttling on the ethereum-bridge either.
Hi @genievot - the Provable oracle service has no mining requirements. Another Provable project, the pTokens, are currently progressing towards the next phase in which external validators are required. You can learn more about this project here: https://ptokens.io/
Are there any grant programs you have to support the use of Provable for my project?
@oraclize-support can you please forward me the links where I can read what nodes process our query?
the queries are currently processed by our nodes but backed by authenticity proofs so you can have guarantees the data is authentic and hasn't been tampered with - we have done tons of presentations in the past few years to explain how they work (look on youtube for oraclize/provable), but here is a good starting point for you: http://docs.provable.xyz/#security-deep-dive
one more thing @oraclize-support can I have multiple callback functions in a single contract?
@genievot - please do keep us informed! As for multiple
__callback functions, your contract can only have the one which the Provable service will use to callback to. However you can use multiple different types of Provable calls in your contract. Then, by tracking the queryIds of those calls, you can have logic in your __callback function to change behaviour depending on which of your Provable queries is calling back. In this way you can mimic the effect of having multiple different __callback functions.