Timeline for Multi node replication
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 1, 2018 at 16:30 | comment | added | Rob Hitchens | Oracles sign a transaction and inject their input into contracts. | |
| Aug 1, 2018 at 16:29 | comment | added | Rob Hitchens | Have a look over here for a few descriptions of the process: ethereum.stackexchange.com/questions/11589/… | |
| Aug 1, 2018 at 16:28 | comment | added | Rob Hitchens | Misunderstanding. Contract functions are deterministic and it is not possible to create a function that produces different outputs at the same block height. As such, it is not possible to consult an external data source. The Oracle pattern uses an external actor to speak to the contract at a specific point. The Oracle's input then becomes a fact on the chain. It will not be consulted when nodes catch up. They will know what the Oracle said at the time, and that's all that matters. | |
| Aug 1, 2018 at 5:12 | comment | added | basilji | Hi Rob,The data which we are getting out of oracles will be different time to time, so if it executes the oracles during catch up there is a chance of state variable value conflict. In this case catch up will fail. Let me know is my understanding is correct or not | |
| Jul 25, 2018 at 7:17 | comment | added | Rob Hitchens | Oracles insert transactions in the usual way, so it will find out what the Oracle said when it catches up to the block when the Oracle said it. | |
| Jul 25, 2018 at 4:50 | comment | added | basilji | Hi Rob, How this will work in the case if we use oraclize in smartcontract | |
| Jul 19, 2018 at 9:22 | history | answered | Rob Hitchens | CC BY-SA 4.0 |