A reference guide to common terminology used throughout the gno.land ecosystem. Terms are listed in alphabetical order.
Application Blockchain Interface - the interface that connects the Tendermint consensus engine with the Gno application logic.
A set of queries that can be executed to retrieve data from the gno.land blockchain without changing state. See Querying a network.
A unique number given to each address on a given network, used for transaction processing and authentication.
A unique identifier derived from a public key, prefixed with 'g1' on gno.land networks, representing an account that can own assets and interact with the blockchain.
A browser extension wallet designed specifically for interacting with gno.land networks. See Third-party wallets.
Data structure in Gno which is commonly used instead of the native map. Found
at gno.land/p/demo/avl.
A Tendermint2 module that is natively embedded into the Gno language, via the
std package. Used for manipulating Coins within Gno.
A fundamental unit in a blockchain that contains a collection of validated transactions, a timestamp, and a cryptographic hash referencing the previous block. This structure ensures the integrity and immutability of the blockchain.
A distributed ledger that records totally ordered transactions, linking the records together via cryptographic hashes. Each block contains transaction data, a timestamp, and a hash of the previous block, forming a continuous chain of immutable records.
A popular on-chain forum application on gno.land that demonstrates social functionality. See Example Boards.
A unique identifier for a blockchain network (e.g., "portal-loop" for the main gno.land testnet).
In gno.land, coins are native assets created by the Banker, such as ugnot. On
the other hand, tokens are created with packages such as GRC20, GRC721, etc.
See Realm.
Decentralized Application - an application built on blockchain technology, typically consisting of smart contracts (realms in gno.land) and a frontend interface.
The process of uploading code to the blockchain. On gno.land, this is done using
the gnokey maketx addpkg command or through compatible wallets.
A web service that provides test tokens for gno.land testnets, allowing developers to try out realms and test transactions. Visit the Gno Faucet Hub.
A unit that measures the computational and storage resources required to execute operations on the blockchain. Used to calculate transaction fees and prevent spam. See Gas Fees for detailed information.
The amount paid per unit of gas, denominated in ugnot. For example, "1000000ugnot" means 1 GNOT per unit of gas.
The maximum amount of gas a transaction is allowed to consume. If a transaction exceeds this limit, it fails without changing state.
- The programming language used for writing smart contracts on gno.land.
- The broader platform and ecosystem built around the language.
A tool that helps developers test and debug Gno smart contracts by allowing them to step through code execution. It lets you pause, inspect variables, and see how your contract behaves before deployment.
A JavaScript/TypeScript client implementation that allows developers to interact with Gno chains. This client library serves as the primary tool for JavaScript applications to communicate with and build on top of the Gno blockchain.
A simple web interface that lets you write, test, and experiment with your Gno code to improve your understanding of the Gno language. You can share your code, run unit tests, deploy your realms and packages, and execute functions. Try out Gno Playground.
A tool that provides seamless access to realms, making it simple to explore, interact, and engage with gno.land's smart contracts through function calls. Try out Gno Studio Connect.
Gno.land's built-in testing framework that enables developers to write and execute unit tests for their Gno smart contracts (realms). It provides a structured way to verify contract logic and simulate on-chain execution.
The blockchain platform and ecosystem built on the Gno language and GnoVM.
A protocol that allows external wallets and applications to interact with gno.land networks, similar to WalletConnect in Ethereum.
A development tool which provides a local gno.land node with hot-reloading,
state preservation, and a gnoweb interface for testing.
See Local Development with gnodev.
The official command-line keychain and client for gno.land, allowing keypair management, transaction signing and sending queries to gno.land chains. See Interacting with gnokey.
The virtual machine that interprets Gno, a custom version of Go optimized for blockchains, featuring automatic state management, full determinism, and idiomatic Go. Unlike traditional VMs, it interprets the abstract syntax tree directly rather than using bytecode.
The web interface component of the Gno ecosystem that allows users to browse Gno source code, realms, and packages deployed to a gno.land chain using ABCI queries. See Exploring with gnoweb.
The native token of gno.land networks, used for paying transaction fees and other on-chain operations.
A token standard in gno.land that defines rules for creating and managing fungible tokens. It ensures compatibility for transfers, approvals, and interactions within gno.land realms.
A combination of a private key (for signing transactions) and a public key (from which the address is derived) that represents an account on gno.land.
The process of organizing data into a Merkle tree structure, allowing efficient and secure verification of large data sets.
A series of words (usually 12 or 24) that can regenerate a private key. Also known as a seed phrase or recovery phrase.
A unique identifier that allows users to exclusively deploy contracts under their own name, similar to usernames on GitHub. See Users and Teams.
A collection of related code that provides specific functionality, similar to libraries in other languages. Pure packages don't maintain state. See Gno Packages.
A unique identifier of code on the gno.land blockchain, following the format:
gno.land/[r|p]/[namespace]/[name]. The package path determines where the code
is stored and how it can be imported or accessed.
The main gno.land testnet, accessible at gno.land.
A stateless, importable, and reusable code (library) on the gno.land
blockchain. Pure packages are stored under the /p/ path and don't maintain
state.
A stateful application or smart contract on the gno.land blockchain. Realms are
stored under the /r/ path and can maintain state across transactions.
A special function in Gno with the signature func Render(path string) string
that returns HTML-like or Markdown content for displaying in web browsers when
the realm is viewed through gnoweb. The path parameter enables different pages
to be returned based on the path.
Number of transactions executed previously by a specific account, also known as nonce. Used to protect against replay attacks.
See Realm.
Built-in packages that provide core functionality to Gno programs without requiring imports from the blockchain. See Standard Libraries.
The persistent data stored by a realm. Each realm has its own isolated state that can only be modified by functions within that realm.
The consensus engine used by gno.land to secure the network and validate transactions.
Minimalistic version of Tendermint created by Jae Kwon, used as the consensus layer for gno.land.
A blockchain network used for testing purposes, where tokens have no real-world value. gno.land currently operates several testnets.
A state-changing action on the gno.land blockchain, such as transferring tokens or calling a realm function.
The smallest unit of GNOT. 1 GNOT = 1,000,000 ugnot (micro-GNOT).
A system realm that allows users to register usernames and claim matching
namespaces for deploying code. List of releases found at gno.land/r/gnoland/users.
See Users and Teams for details.
Wrapped version of ugnot, following the GRC20 standard.