Search Results

The only reference to temporal time we have is the block timeStamp which is somewhat subjective (caution) since it is placed there by the miner. Hope it helps. …

Since no one can check the timeStamp without reference to a non-deterministic time source, the accuracy of the time stamp is dubious. … There's an interesting discussion on the accuracy of the timeStamp, the latitude the miners have and incentives to keep the timeStamp within reason, here: How do Ethereum mining nodes maintain a time consistent …

Miners record a block timeStamp with each discovered block. This value cannot be confirmed or disproved by observers without reference to an accurate external time source, which we do not want. … Second, the clock must never run backward, so the timestamp of a new block should always come after the time stamp of the previous block in the chain. …

You cannot ensure the miners accept transactions in the intended order, but you can check and reject if they don't. You would make each new transaction dependent on something that came earlier. Here …

In my opinion it might be helpful to reframe the question with a little more precision. When you say "I need to", it creates a little doubt about what's supposed to happen. It's hard to say if you n …

Yes, but with some nuances so the guarantees are well understood. Event log entries are part of the transactions in blocks. As such, you can reason about event sequence assurances with the same princi …

The moment this is deemed to have taken place is the timestamp for the block. …

and the timestamp signed by the contract itself. … The transaction the signer (creator) sent was mined into a block with a definite timeStamp. …

Most use-cases can be solved by inverting control. Rather than having the contract run something at a certain time, interested parties claim entitlements when appropriate. The contract decides if the …