Skip to main content
Ethereum

Return to Question

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

My contract depends on checking to see if an expiration period has expired before sending the contracts balance. I was looking at the ConsenSys best practices here and it says:

Timestamp Dependence

 

Be aware that the timestamp of the block can be manipulated by the miner, and all direct and indirect uses of the timestamp should be considered. Block numbers and average block time can be used to estimate time, but this is not future proof as block times may change (such as the changes expected during Casper).

Is there any way around this? It seems like it would be quite a hinderance to the idea of smart contracts since contracts are often heavily reliant on time.

My contract depends on checking to see if an expiration period has expired before sending the contracts balance. I was looking at the ConsenSys best practices here and it says:

Timestamp Dependence

 

Be aware that the timestamp of the block can be manipulated by the miner, and all direct and indirect uses of the timestamp should be considered. Block numbers and average block time can be used to estimate time, but this is not future proof as block times may change (such as the changes expected during Casper).

Is there any way around this? It seems like it would be quite a hinderance to the idea of smart contracts since contracts are often heavily reliant on time.

My contract depends on checking to see if an expiration period has expired before sending the contracts balance. I was looking at the ConsenSys best practices here and it says:

Timestamp Dependence

Be aware that the timestamp of the block can be manipulated by the miner, and all direct and indirect uses of the timestamp should be considered. Block numbers and average block time can be used to estimate time, but this is not future proof as block times may change (such as the changes expected during Casper).

Is there any way around this? It seems like it would be quite a hinderance to the idea of smart contracts since contracts are often heavily reliant on time.

Source Link
Daniel Kobe
Daniel Kobe
  • 1.6k
  • 2
  • 14
  • 14

Solidity: Timestamp dependency, is it possible to do safely?

My contract depends on checking to see if an expiration period has expired before sending the contracts balance. I was looking at the ConsenSys best practices here and it says:

Timestamp Dependence

Be aware that the timestamp of the block can be manipulated by the miner, and all direct and indirect uses of the timestamp should be considered. Block numbers and average block time can be used to estimate time, but this is not future proof as block times may change (such as the changes expected during Casper).

Is there any way around this? It seems like it would be quite a hinderance to the idea of smart contracts since contracts are often heavily reliant on time.