Crates.io | noble-timestamp |
lib.rs | noble-timestamp |
version | 2.0.0 |
source | src |
created_at | 2021-04-04 04:53:08.167249 |
updated_at | 2021-04-04 04:53:08.167249 |
description | FABRIC Timestamp Module |
homepage | https://core.tetcoin.org |
repository | https://github.com/tetcoin/tetcore |
max_upload_size | |
id | 378620 |
size | 23,393 |
The Timestamp module provides functionality to get and set the on-chain time.
The Timestamp module allows the validators to set and validate a timestamp with each block.
It uses inherents for timestamp data, which is provided by the block author and validated/verified by other validators. The timestamp can be set only once per block and must be set each block. There could be a constraint on how much time must pass before setting the new timestamp.
NOTE: The Timestamp module is the recommended way to query the on-chain time instead of using an approach based on block numbers. The block number based time measurement can cause issues because of cumulative calculation errors and hence should be avoided.
set
- Sets the current time.get
- Gets the current time for the current block. If this function is called prior to
setting the timestamp, it will return the timestamp of the previous block.MinimumPeriod
- Gets the minimum (and advised) period between blocks for the chain.The following example shows how to use the Timestamp module in your custom module to query the current timestamp.
Import the Timestamp module into your custom module and derive the module configuration trait from the timestamp trait.
use fabric_support::{decl_module, dispatch};
use fabric_system::ensure_signed;
pub trait Config: timestamp::Config {}
decl_module! {
pub struct Module<T: Config> for enum Call where origin: T::Origin {
#[weight = 0]
pub fn get_time(origin) -> dispatch::DispatchResult {
let _sender = ensure_signed(origin)?;
let _now = <timestamp::Module<T>>::get();
Ok(())
}
}
}
The Session module uses the Timestamp module for session management.
License: Apache-2.0