Skip to main content

Glossary

Abstract syntax tree​

An abstract syntax tree (AST) is a formal representation of an Approval Rule definition. This is how it's created:

  1. A user defines a new Approval Rule in the Intent-Specific Language.
  2. A tokenizer breaks the Approval Rule into tokens representing the smallest elements of the Intent-Specific Language.
  3. A parser validates the syntactic structure of the definition and represents it as an AST, which is stored onchain.

Action​

An Action is an onchain transaction on Warden Protocol or an offchain operation, such as creating a post on the X network. An Action is executed after an Approval is granted based on a user-defined Approval Rule, as specified in an Intent.

To perform an onchain Action, one can use SpaceWard, run node commands, or prompt a Warden AI Agent. Here are some examples of onchain Actions:

This concept is implemented in the x/act module. Learn more: x/act.

Agent network​

The Agent network is the infrastructure that supports the entire lifecycle of AI Agents. It provides the full-stack foundation for the Agent economy, unifying Agents that would otherwise remain fragmented across frameworks and custom stacks without reaching users.

The core elements of the Agent network are Warden Studio, Warden Chain, Warden Agent Hub, and Warden.

AI Agent​

An AI Agent is an AI-driven program that supports both offchain and onchain operations. Agents perform complex Actions through simple chat commands—for example, bridging, minting, trading, staking, deep research. At the moment, we focus on financial, autopilot, institutional (custodial), and ecosystem Agents.

We capture the entire life cycle of Agents in our Agent network through these core elements: Warden Studio, Warden Chain, Warden Agent Hub, Warden.

Analyzer​

An Analyzer is a CosmWasm contract that intercepts a payload before it's signed by a Keychain.

Using Analyzers allows Keychains to receive the final payload without the need to have any knowledge of its content. Analyzers can extract payload metadata and manipulate the payload before it's signed.

This concept is implemented in the x/warden module. Learn more: x/warden.

Approval​

An Approval is a permission for an Action to be performed. Approvals are granted according to user-defined Approval Rules.

Approval Rule​

An Approval Rule is a set of user-defined conditions under which an Action is performed. For example, a Rule can allow executing a transaction only if 2 of 3 approvers sign it.

You can define Approval Rules as part of Intents, using the Intent-Specific Language. Warden's Intent Engine ensures the validity of transactions by checking Rules, represented as abstract syntax trees.

This concept is implemented in the x/act module. Learn more: x/act.

AVR Plugin​

An AVR Plugin, or Asynchronous Verifiable Resource, is code determining what kind of Task input to accept and how to handle it in order to retrieve the result (output). Plugins are executed by Prophets.

Developers can create their own Plugins or use the existing ones. Currently, we support two Plugin types, which allow executing the following Task types:

  • AI-driven price predictions (verified by SPEX)
  • HTTP requests to external services, such as blockchain APIs

AVR Plugins provide a universal and standard way for smart contracts to access any resource or operate offchain systems. This concept is implemented in the x/async module. Learn more: x/async.

Big Brain​

Big Brain (under development) is a protocol-enabled, domain-specific LLM trained on 1T tokens, catalyzing AI Agent performance as the evolving hive mind. Big Brain learns from every Warden interaction and rewards contributors who help it improve.

Blockchain layer​

The blockchain layer provides the core infrastructure for AI Agents: identity, coordination, and provenance. Agents are deployed directly onto Warden Chain.

Bonded validator​

A bonded validator is an active validator participating in consensus (staking). Bonded validators validate transactions, propose blocks, and earn rewards for their contributions to the network.

See also: Unbonding validator, Unbonded validator.

Builder incentive​

Warden Protocol is open to third-party contributions: core protocol development or building Intelligent Applications in the Warden ecosystem. We'll reward both types of contributions with builder incentives in WARD. More details will be announced soon.

Delegator​

A delegator is an individual or entity that participates in the staking process by delegating their WARD tokens to a validator. Delegation allows securing the network and sharing rewards with validators without the responsibility of running a node.

All delegators inherit the state from their validator: bonded, unbonding, or unbonded. To avoid risks, delegators should perform due diligence on validators and spread their stake over multiple validators. Delegators can also participate in governance.

Full node​

A full node is a server running a software (binary) that maintains a complete up-to-date version of a protocol with full transaction history. You can run a full Warden Protocol node yourself.

Governance​

Warden Protocol supports onchain governance. It's a mechanism allowing the decentralized community to update the protocol through direct voting that is recorded onchain. Voting is available for the participants of staking: validators and delegators.

The voting power depends on the validator's weight or the amount of WARD a delegator staked. By default, delegators inherit votes of their validator. Alternatively, a delegator can cast their own vote, which will reduce the validator's voting power.

Intelligent Application​

An Intelligent Application is a smart contract integrating AI or any offchain logic. Unlike traditional contracts bound by static logic, Intelligent Apps unlock more dynamic user experiences: they're able to reason, adapt, and interact across onchain and offchain environments.

With Warden, you can build crypto super apps, smart AI Agents, and intelligent custody solutions. For example, see SpaceWard and Warden.

We support two smart contract platforms: EVM and CosmWasm. In contracts, you can interact with our modules and AVR Plugins to access all Warden's core features from any chain. For advanced usage of smart contracts, refer to Order.

Learn more: Warden Manifesto, Build an app, Build an Agent.

Intent​

An Intent is a user-defined script specifying the following:

  • An Action—any onchain action on Warden Protocol
  • An Approval Rule—a set of conditions under which the Action is performed

After an Action is initiated, the Intent Engine checks the Approval Rule. If the conditions are met, an Approval is granted, and the Action is carried out.

Intent Engine​

The Intent Engine is an immutable onchain interpreter of the Intent-Specific Language, acting as a gatekeeper. When a user initiates a transaction (Action), the Intent Engine checks the user's Approval Rule, represented as an abstract syntax tree, and returns true or false—granting or not granting an Approval.

Intent-Specific Language​

The Intent-Specific Language (ISL) is a language that allows users to configure Approval Rules (as part of Intents). It's composable, extensive, declarative, human-readable, and English-like. The ISL is interpreted by the Intent Engine.

Interoperability​

Interoperability is the ability of different blockchains to communicate and exchange data or assets. Warden supports it through integration with Hyperlane, a leading modular interoperability framework.

This collaboration makes the output from Warden's AVR Plugins universally accessible across 150+ blockchains—from Ethereum and Solana to Cosmos-based ecosystems and beyond. This enables developers to access verifiable AI anywhere.

Learn more: Interoperability.

Key​

Keys in blockchain are paired to identify users and secure the ownership of wallets:

  • Public key: A public wallet address
  • Private key: A private code for signing transactions on the wallet

On Warden, Keychains generate key pairs and sign transactions with private keys. Every key belongs to a certain Space.

This concept is implemented in the x/warden module. Learn more: x/warden.

Key request​

A key request is a request asking a Keychain to generate a pair of private and public keys. Keychain operators can charge key request fees for doing it. This is how such requests are processed:

  1. A user sends a key request with a Keychain ID identifying the preferred Keychain.
  2. The Intent Engine checks the user's Approval Rule, specified in an Intent.
  3. If the Approval Rule is met, the Keychain generates a key pair and stores the private key. A Keychain Writer publishes the public key to Warden Protocol.

Learn more: Key request flow.

Key request fee​

Keychain operators can set fees in WARD for key requests. The Keychain collects fees to its ID, and then the Keychain operator can manage these funds. Key request fees are indicated in aWARD (0.000000000000000001 WARD).

Keychain​

Every Intelligent Application has at least one Keychain—a custodian that generates and stores keys and signs transactions on any chain. This helps avoiding manual crosschain coordination.

Warden Protocol allows users or external organizations to become Keychain operators. They can onboard their own Keychains and charge fees for key requests and signature requests. Note that Keychain operators typically use MPC networks to generate keys and signatures.

This concept is implemented in the x/warden module. Learn more: x/warden, Build a Keychain.

Keychain ID​

Keychain ID identifies a Keychain in key requests and signature requests and collects fees from users.

Keychain Writer​

A Keychain Writer is an account that publishes signatures and public keys on behalf of a Keychain. It happens when the Keychain responds to a key request or a signature request. The Keychain operator can create multiple Writers, each with its own address.

Keychain SDK​

The Keychain SDK is a Go SDK that abstracts the communication with Warden Protocol nodes, facilitating the development of Keychains.

Learn more: Keychain SDK.

Module​

Warden protocol modules are Cosmos SDK modules containing most of Warden Protocol's logic. Users can interact with modules by sending transactions or querying nodes. We also provide precompiles that allow Intelligent Application builders to call certain modules in EVM smart contracts.

Learn more: Warden Protocol modules.

Node​

A Warden Protocol node is a server running the software (binary) of Warden Protocol. To run a blockchain node in Warden, build and run the chain binary called wardend. To interact with a node, use the Node API and node commands.

Reasons for running a node include the following:

  • Accessing archive data
  • Providing services: RPC, GRPC, API, etc.
  • Becoming a validator

Oracle service​

An oracle is a third-party service that enables smart contracts to access real-life data feeds: prices, stock market data, weather conditions, etc. Warden is integrated with Skip:Connect—an oracle service provided by Skip Protocol and offering mostly price data. Connect's data is validated by Warden's network and written onchain.

Learn more: Oracle services.

Order​

An Order is a Solidity smart contract performing onchain actions at any destination chain.

When creating an Order, you can implement custom logic by using Warden modules, Keychains, and other features. In particular, the x/async module with AVR Plugins allows you to create smart contracts utilizing outputs of AI models. Orders can send any transactions to any Ethereum-based and EVM L2 application.

Learn more: Build an onchain AI Agent.

Precompile​

Warden precompiles are precompiled smart contracts that you can call in your EVM smart contract to interact with Warden Protocol modules. This allows Intelligent Application builders to manage Spaces, Keychains, Actions, Rules, Tasks, and other components.

Learn more: Interact with Warden modules.

Prophet​

A Prophet is a subprocess running on validator nodes, which has two responsibilities:

  • Fetching Task requests and executing AVR Plugins to provide Task results
  • Fetching requests satisfied by other validators to vote on the results

Prophets run on validator nodes separately from the wardend process, without blocking the consensus. Running a Prophet is optional for a validator.

This concept is implemented in the x/async module. Learn more: x/async.

Signature request​

A signature request is a request asking a Keychain to sign a transaction with a private key. Keychain operators can charge signature request fees for doing it. This is how such requests are processed:

  1. A user sends a signature request with a Keychain ID identifying the preferred Keychain.
  2. The Intent Engine checks the user's Approval Rule, specified in an Intent.
  3. If the Approval Rule is met, a Keychain Writer publishes a signature to Warden Protocol.

Learn more: Signature request flow.

Signature request fee​

Keychain operators can set fees in WARD for signature requests. The Keychain collects fees to its ID, and then the Keychain operator can manage these funds. Signature request fees are indicated in aWARD (0.000000000000000001 WARD).

Space​

A Space is a hub allowing its owner (or multiple owners) to manage keys. Spaces aggregate accounts for different blockchains and provide access to Intelligent Applications.

This concept is implemented in the x/warden module. Learn more: x/warden.

SpaceWard​

SpaceWard is an Intelligent Application functioning as the front-end interface for Warden. It provides a user-friendly platform where you can create Spaces, manage wallets and Intents, and interact with decentralized applications (dApps) and other components of the Web3 ecosystem.

Learn more: SpaceWard documentation.
Try it out: SpaceWard.

SPEX​

SPEX (Statistical Proof of Execution) is a sampling-based verifiable computing protocol that ensures the integrity of computational tasks through probabilistic guarantees. This includes tasks with potentially non-deterministic outputs, such as those involving large language models (LLMs) or stochastic training pipelines.

SPEX is used as a verifiability layer for AI on Warden Protocol. At the moment, SPEX verifies AI-driven price predictions generated by the x/async Warden module and AVR Plugins. However, you can extend the module with other computational tasks and use SPEX to protect them.

Learn more: SPEX.

Staking​

Staking is the process of participating in the proof-of-stake (POS) consensus mechanism. Validators and delegators stake their WARD tokens for a chance to validate blocks and transactions and earn staking rewards.

The consensus mechanism chooses validators based on their weight. If a validator is successful, its delegators will earn rewards too. If a validator is slashed, the delegator’s stake will be slashed. Staking also allows validators and delegators to participate in governance.

Task​

A Task is an offchain user-defined unit of computation that is executed asynchronously. The result is stored onchain. Tasks don't slow the blockchain down thanks to asynchronous execution.

A user requests a Task, specifying an input and an AVR Plugin, which determines what format of input to accept and how to handle it. There are different types of Tasks, depending on the Plugin type. After that, a validator running a Prophet executes the Plugin and provides the Task result, and other validators vote on correctness of the result.

This concept is implemented in the x/async module. Learn more: x/async.

Validator​

A validator is an individual or entity that participates in the staking process by running a full or pruned Warden Protocol node and validating blocks and transactions.

Validators act on behalf of their delegators and earn commissions. Each validator has a certain weight and state: bonded, unbonding, or unbonded. Validators can also participate in governance and hadling Tasks.

Validator's commission​

A validator’s commission is the percentage of staking rewards earned by a validator's pool that the validator retains. The rest is distributed to delegators. Validators can configure their own commissions, but only once, when initially declaring candidacy. The following parameters are available:

  • An initial commission
  • A maximum daily commission change rate
  • A maximum commission

Validator's weight​

Each validator has its own WARD tokens and tokens bonded by its delegators. The total amount of tokens determines the validator's weight.

The consensus mechanism selects validators to propose blocks based on validators' weight, so a validator with more tokens bonded can propose blocks more frequently and generate more rewards. Weight also determines the validator's voting power in governance.

Unbonded validator​

An unbonded validator is an inactive validator that isn't signing blocks. Unbonded validators can't be slashed and can’t earn rewards.

See also: Bonded validator, Unbonding validator.

Unbonding validator​

An unbonding validator is a validator that is transitioning from bonded to unbonded.

Validators enter this state either when they decide to stop participating in staking or when they're slashed for misbehavior. During the unbonding period, validators aren't participating in the consensus process and aren't earning rewards.

WARD token​

$WARD is the native utility token for the Warden ecosystem, sitting at the heart of both Warden Protocol and Warden. $WARD facilitates various operations—such as governance, staking, rewards—and serves as a medium of payment for any developer publishing an Agent on Warden. For Warden, it'll act as a gas abstraction token and unlock gated functionality.

Learn more: $WARD.

Warden​

Warden is an AI-driven Intelligent Application built on Warden Protocol. In Warden, users access all AI Agents, models, and chains through a single interface, performing advanced workflows in natural language. Agents are available in Warden Agent Hub.

Learn more: Warden documentation.
Try it out: Warden.

Warden Agent Hub​

Warden Agent Hub is a marketplace in Warden where users discover AI Agents operating across Web2 and Web3 ecosystems. By putting Agents in front of an engaged user base, the Hub solves the toughest challenge in tech: distribution. Moreover, Agents listed here can collaborate to solve complex problems.

Learn more: Warden documentation.

Warden Agent Kit​

The Warden Agent Kit allows creating AI Agents that are able to access both offchain and onchain functionalities. The kit offers native integration with Warden Protocol for onchain Actions and supports compatibility with Typescript, any AI Agent framework, and LangChain tools.

Learn more: Warden Agent Kit.

Warden Chain​

Warden Chain serves as an entry point to discover, interact , and transact with AI Agents in our ecosystem. Once an Agent is built, it gets minted directly onto the chain, where it signs requests, collects fees, and pays for services.

Learn more: Warden networks.

Warden Studio​

Warden Studio (now in Alpha) is a toolkit giving builders everything they need to develop, test, and publish AI Agents directly to Warden users—from decentralized, verifiable inference to domain-specific language models, verification systems, and core primitives. This toolkit is built for Web3 developers, no-code creators, and Web2 builders.