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
  • Consensus
  • Functions

Was this helpful?

  1. Modules
  2. Pre-built

Aura

Wrapper module for consensus

PreviousPre-builtNextBalances

Last updated 4 years ago

Was this helpful?

Overview

The Aura module extends Aura consensus by providing set of utility functions.

Consensus

Aura, also known as Authority-round, is a consensus in Substrate. It works by providing list of authorities who are expected to roughly agree on the current time. Aura works by having a list of authorities A who are expected to roughly agree on the current time. Time is divided up into discrete slots of t seconds each. For each slot s, the author of that slot is A[s % |A|]

The author is allowed to issue one block but not more during that slot, and it will be built upon the longest valid chain that has been seen.

Blocks from future steps will be either deferred or rejected depending on how far in the future they are.

NOTE: Aura itself is designed to be generic over the crypto used.

For more, visit Aura .

Functions

  • _getSlotDuration(): Moment - gets the configured Slot Duration

  • _getAuthorities(): u8[] - gets list of Authorities as SCALE encoded bytes

  • _checkInherent(t: Moment, data: InherentData): bool - verifies the validity of the inherent using the timestamp

docs