MinaSearch
  • Getting Started
    • Overview
    • Data Exploration
  • APIs
    • GraphQL
    • REST
    • HTTP
  • Terminology
    • Definitions
    • Glossary
  • Legal
    • Terms of Service
    • Disclaimer
Powered by GitBook
On this page
  • Height
  • User Command Status
  • Block Canonicity
  • Mina Indexer Specific
  1. Terminology

Definitions

PreviousHTTPNextTerms of Service

Last updated 2 months ago

Height

Height is used with blockchain length.

User Command Status

User commands can be Applied or Failed and this status is determined at the time a block is produced. Thus, user command status does not depend on canonicity.

All user commands require a > 0.0 fee.

No fees are paid unless a block is canonical.

  • Applied

  • Failed

    • Why? One possible failure reason could be insufficient funds.

Block Canonicity

Canonicity is an emergent property, because a block is only canonical or non-canonical in retrospect.

  • Canonical: The best block or a descendant of the best block

  • Pending: Transaction that has been gossiped and buffered in a Node's mempool

  • Finalized: Transaction/block has > k (=290) confirmations

Mina Indexer Specific

  • Deep Canonical: Canonical blocks with a minimum of x threshold confirmations

  • Recent: Any blocks (in the provided directory) that have a higher height (blockchain length) than the highest Deep Canonical block

The following information will be most helpful for developers working on .

interchangeably
Mina Indexer