subsembly
  • Introduction
  • Getting Started
    • Overview
    • Substrate Essentials
    • CLI
      • subsembly init
      • subsembly compile
      • subsembly spec
  • Development
    • Runtime Development
    • Chain Specification
    • Runtime Execution
  • Modules
    • Core
      • System
      • Executive
      • Crypto
      • Log
    • Pre-built
      • Aura
      • Balances
      • Timestamp
      • TransactionPayment
  • Advanced
    • as-scale-codec
    • subsembly-core
    • Metadata
      • Dispatcher
  • Guides
    • Create Your First Subsembly Runtime
      • Set Up
      • Start the Node
      • PolkadotJS
    • Start Your Network
      • Prepare the Network
      • Launch Validator Nodes
      • Launch the Third Node
    • Create a New Module
      • Nicks Module
      • Launch the Node
      • PolkadotJs
Powered by GitBook
On this page
  • Overview
  • Dispatchable Calls
  • Configuration

Was this helpful?

  1. Modules
  2. Pre-built

Timestamp

Get and set on-chain time

Overview

The Timestamp pallet 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.

Dispatchable Calls

  • set - sets the current time. When setting the new time, it must be greater than the last one (set into storage) with at least a MinimumPeriod

Configuration

Timestamp requires to set following constants during the runtime initialisation:

  • minimumPeriod - minimum period between timestamps. Also, minimal interval between two blocks.

PreviousBalancesNextTransactionPayment

Last updated 4 years ago

Was this helpful?