# Gen

> Developer documentation for Gen, a Layer 1 blockchain for agentic payments. Covers concepts, CLI, RPC, SDKs, and tutorials for building agent-driven payment applications.

## Docs

- [Platform changelog](https://docs.genlabs.co/changelog/platform.md): Notable changes to the Grid platform: networks, RPC, CLI, and SDKs.
- [Quickstart](https://docs.genlabs.co/quickstart/index.md): Install the CLI, create a wallet, fund it, send your first transfer, and confirm the result in five minutes.
- [llms.txt](https://docs.genlabs.co/reference/ai/llms-txt.md): Machine-readable index of the Grid documentation for LLMs and AI agents.
- [Working with activations](https://docs.genlabs.co/reference/cli/activations.md): Build, sign, simulate, submit, and inspect activations from the command line.
- [Client queries](https://docs.genlabs.co/reference/cli/client-queries.md): Read on-chain state (accounts, balances, blocks, contracts, components, storage) from the CLI.
- [CLI configuration](https://docs.genlabs.co/reference/cli/configuration.md): Configure the gen CLI: RPC endpoint, default headers, and where the config file lives.
- [Install the CLI](https://docs.genlabs.co/reference/cli/install.md): Download the gen binary, put it on your PATH, and verify the install.
- [Sending transfers](https://docs.genlabs.co/reference/cli/transfers.md): CLI surface for moving GEN, checking balances, and requesting faucet funds.
- [CLI Wallet](https://docs.genlabs.co/reference/cli/wallet.md): Manage local Grid wallets: create, import, list, switch, rename, remove, and export keys.
- [Grid framework reference](https://docs.genlabs.co/reference/contracts/genesis-framework.md): Audited, reusable contract primitives for the GVM. Includes the fungible-token protocol and the component-role patterns it exemplifies.
- [Genie SDK reference](https://docs.genlabs.co/reference/contracts/genie-sdk.md): Component-based contract development for the GVM. Macros, storage, runtime, and communication APIs.
- [Contract test tools reference](https://docs.genlabs.co/reference/contracts/test-tools.md): Validator modes, test fixtures, and integration testing patterns from the `gen-test-tools` crate.
- [JSON-RPC API](https://docs.genlabs.co/reference/rpc/overview.md): Full JSON-RPC reference for the Grid: every method, parameter, and response shape.
- [Rust SDK](https://docs.genlabs.co/reference/sdk/rust.md): Typed Rust client for the Grid JSON-RPC API: connect, query, sign, and submit activations from your own service or agent.
- [TypeScript SDK](https://docs.genlabs.co/reference/sdk/typescript.md): TypeScript client SDK for the Grid.
- [Contracts](https://docs.genlabs.co/reference/troubleshooting/contracts.md): ABI validation surprises, dependency-resolution failures after a fresh init, and CLI signer-missing errors.
- [Devcontainer](https://docs.genlabs.co/reference/troubleshooting/devcontainer.md): GitHub auth failures, docker exec PATH gotchas, and rust-analyzer not surfacing errors inside the workshop devcontainer.
- [Toolchain](https://docs.genlabs.co/reference/troubleshooting/toolchain.md): Rust version mismatches, stale RISC-V remnants, and gen genie build caching upstream changes.
- [Validator](https://docs.genlabs.co/reference/troubleshooting/validator.md): Local validator startup gotchas, stale processes blocking tests, and CLI/SDK failing to reach the RPC endpoint.
- [Your first account](https://docs.genlabs.co/tutorials/cli-sdk/01-your-first-account.md): Two commands to a working on-chain identity. Zero activations spent.
- [Fund it from the faucet](https://docs.genlabs.co/tutorials/cli-sdk/02-fund-from-the-faucet.md): One activation, sub-cent cost, identity goes live.
- [Local → DevNet in one flag](https://docs.genlabs.co/tutorials/cli-sdk/03-local-vs-devnet.md): The same commands you just ran, but on a real shared network. The diff is one URL and one header.
- [Transfer between two accounts](https://docs.genlabs.co/tutorials/cli-sdk/04-transfer-between-accounts.md): The build-activation → sign-and-submit pattern. The one pattern that powers every write on the Grid.
- [Deploy a contract from ABI](https://docs.genlabs.co/tutorials/cli-sdk/05-deploy-a-contract-from-abi.md): Push compiled artifacts, deploy an instance, install the holder — all from the CLI.
- [Calling your contract](https://docs.genlabs.co/tutorials/cli-sdk/06-call-your-contract.md): Reads are free. Writes are one activation. That's the whole interface.
- [Environment Setup](https://docs.genlabs.co/tutorials/cli-sdk/environment-setup.md): Install the gen toolchain so the rest of the curriculum can run.
- [Overview](https://docs.genlabs.co/tutorials/cli-sdk/overview.md): From your first account to an agent acting on-chain, in under an hour.
- [Adding Functionality](https://docs.genlabs.co/tutorials/contract-development/adding-functionality.md): Build the simple-token holder: balance, transfer, receive, and access modifiers.
- [Borrowed Code · Make It Compile](https://docs.genlabs.co/tutorials/contract-development/composability.md): Composability, part 1 — wire simple-token into my-token until it compiles.
- [Borrowed Code · Make It Run](https://docs.genlabs.co/tutorials/contract-development/composability-calling.md): Composability, part 2 — default routing, the cross-contract call, and the test that proves it.
- [Environment Setup](https://docs.genlabs.co/tutorials/contract-development/environment-setup.md): Pick one of the two installation paths for the GEN toolchain.
- [To Panic is Human, to Err is Divine](https://docs.genlabs.co/tutorials/contract-development/error-handling.md): Error propagation across async activations — panic doesn't save Alice, Result::Err does.
- [Let's see if you got it](https://docs.genlabs.co/tutorials/contract-development/final-exercises.md): Two capstone exercises — build a smart contract from scratch using everything you've learned.
- [First Build, First Test](https://docs.genlabs.co/tutorials/contract-development/first-build.md): Anatomy of a GEN contract — the root component, the ABI, push & deploy — then your first test.
- [Everything but the Kitchen Sync](https://docs.genlabs.co/tutorials/contract-development/kitchen-sync.md): Sync vs. async, local vs. remote, and how entity boundaries change which one you can use.
- [Overview](https://docs.genlabs.co/tutorials/contract-development/overview.md): A guided, hands-on walkthrough of the Grid smart-contract framework: six chapters, two parallel tracks, one passing test at a time.
- [Project Setup](https://docs.genlabs.co/tutorials/contract-development/project-setup.md): Two parallel projects: a Guided track (simple-token) and an Exercise track (my-token).
- [Cross-contract composition walkthrough](https://docs.genlabs.co/tutorials/recipes/contract-composition-walkthrough.md): Build up a working mental model of entities, components, access control, events, storage, cross-contract composition, and delegated authority through 12 small contracts, each teaching one new idea on top of the last.
- [Deploy a contract to DevNet](https://docs.genlabs.co/tutorials/recipes/deploy-to-devnet.md): Push a built contract to DevNet, deploy an instance, install components, call methods, and query state, using `gen client`.
- [Sign with an external KMS](https://docs.genlabs.co/tutorials/recipes/sign-with-external-kms.md): Use the Grid Rust SDK with an Ed25519 key held in AWS CloudHSM, GCP KMS, Azure Key Vault, HashiCorp Vault, or any external signing oracle; without ever loading the private key into your process.
- [Pay an API from an agent with x402](https://docs.genlabs.co/tutorials/recipes/x402-payment-gate.md): A TypeScript x402 server and buyer that run on the gen CLI alone, both halves settled on The DevNet Grid.
- [Activation structure](https://docs.genlabs.co/user-guide/concepts/activation-structure.md): The fields that make up an activation, what gets signed, and how the validity window replaces a sequential nonce.
- [Activations](https://docs.genlabs.co/user-guide/concepts/activations.md): Activations are how you submit work to the Grid; the equivalent of a transaction on Ethereum.
- [Address format](https://docs.genlabs.co/user-guide/concepts/address-format.md): How Grid encodes entity references as bech32m strings with network-specific prefixes.
- [Components](https://docs.genlabs.co/user-guide/concepts/components.md): Components are the executable units you deploy on the Grid: logic plus local state, installed inside entities.
- [Entities and accounts](https://docs.genlabs.co/user-guide/concepts/entities-and-accounts.md): Every wallet, agent, and service on the Grid is an entity: an addressable container of state and behavior, keyed to a public key.
- [Finality](https://docs.genlabs.co/user-guide/concepts/finality.md): What deterministic finality means, how the Grid delivers it through consensus and replication, and how to wait correctly in your client.
- [Gas and fees](https://docs.genlabs.co/user-guide/concepts/gas-and-fees.md): How the Grid will meter transaction costs across multiple resource dimensions and charge fees in stablecoins. A planned design not yet active on DevNet.
- [Parallel execution](https://docs.genlabs.co/user-guide/concepts/parallel-execution.md): Why independent activity on the Grid runs in parallel, and what that means for someone observing the chain.
- [Shards and clusters](https://docs.genlabs.co/user-guide/concepts/shards-and-clusters.md): How Grid partitions execution across shards and replicates across clusters to achieve concurrent entity processing.
- [Traces](https://docs.genlabs.co/user-guide/concepts/traces.md): A trace is the full spawn-tree of activations produced by one externally submitted activation, identified by a trace ID and queryable as a single unit.
- [The Grid for agent builders](https://docs.genlabs.co/user-guide/concepts/why-gen-for-agents.md): Five concrete properties that make Grid suitable for agent-driven payment workflows.
- [Network status](https://docs.genlabs.co/user-guide/network-status.md): Current status of the Grid networks and available tools.
- [Inline settlement for agent workflows](https://docs.genlabs.co/user-guide/use-cases/agentic-settlement.md): the Grid settles value inside the agent's workflow itself, with sub-second finality and policy enforcement at the chain layer.
- [Discovery and reputation for open agent networks](https://docs.genlabs.co/user-guide/use-cases/discovery-and-reputation.md): the Grid makes trust visible, verifiable, and transferable across agent ecosystems.
- [Identity for agentic systems](https://docs.genlabs.co/user-guide/use-cases/identity.md): the Grid makes agent identity verifiable, portable, and traceable across open networks.
- [Intent verification for autonomous systems](https://docs.genlabs.co/user-guide/use-cases/intent-verification.md): the Grid makes it possible to verify that agent actions stayed within the bounds of real user intent.
- [Micropayments at machine speed](https://docs.genlabs.co/user-guide/use-cases/micropayments.md): the Grid makes sub-cent, real-time payments viable for agents, APIs, and open financial systems.
- [On-chain CLOB for DeFi, with CeFi performance](https://docs.genlabs.co/user-guide/use-cases/onchain-clob.md): the Grid delivers shared clearing, unified liquidity, and instant on-chain responsiveness to DeFi trading.
- [Social and communication infrastructure for agent networks](https://docs.genlabs.co/user-guide/use-cases/social-and-communication.md): the Grid makes agent communication interoperable, verifiable, and auditable across open systems.
- [What is the Grid](https://docs.genlabs.co/user-guide/what-is-gen.md): The Grid is a Layer-1 blockchain for agentic payments: sub-cent fees, sub-second deterministic finality, settled in stablecoins.
- [Who the Grid is for](https://docs.genlabs.co/user-guide/who-its-for.md): the Grid is a Layer 1 for agentic payments. These pages describe the workflows it's built to support.

## OpenAPI Specs

- [openapi](https://docs.genlabs.co/api-reference/openapi.json)