docs.wal.app valid

Walrus Docs

Walrus is a decentralized blob storage protocol built on Sui. It provides robust, cost-effective

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T19:23:47.064Z. Cached copy · Source on docs.wal.app

# Walrus Docs

> Walrus is a decentralized blob storage protocol built on Sui. It provides robust, cost-effective
> storage for large binary objects with high availability guarantees using erasure coding. This
> documentation covers setup, usage, the client CLI, SDKs, on-chain integration, and Walrus Sites
> (decentralized web hosting).

> For the complete, unabridged page index see [llms-full.txt](https://docs.wal.app/llms-full.txt).

Important notes:

- Walrus stores data as **blobs** (immutable byte arrays). All blobs are public; use an encryption
service like Seal for private data.
- Walrus has two networks: **Mainnet** (production, uses real SUI/WAL tokens) and **Testnet** (for
development and testing).
- The `walrus` CLI is the primary client. It supports storing, reading, and managing blobs, and can
run as a local daemon exposing an HTTP API.
- **Walrus Sites** enable fully decentralized web hosting: static assets stored on Walrus, with a
Sui smart contract as the on-chain index.
- Costs involve WAL tokens (for storage) and SUI tokens (for on-chain transactions).

## Getting Started

- [Advanced Setup](https://docs.wal.app/docs/getting-started/advanced-setup.md):
    Advanced installation options for Walrus including building from source and binary
    installation. This page covers advanced setup options for Walrus, including building from
    source, installing from binaries, or using Cargo. For standard setup instructions, see Getting
    Started.
- [Getting Started](https://docs.wal.app/docs/getting-started.md):
    Walrus is a verifiable data platform for high-stakes systems like AI and onchain finance, where
    data is stored as blobs. Walrus uses an object storage architecture, where blobs are stored in
    a flat namespace rather than a hierarchy. There are no folders or directories.

## System Overview

- [Aggregators Publishers Relays](https://docs.wal.app/docs/system-overview/aggregators-publishers-relays.md):
    Walrus exposes three HTTP services. Callers send requests to the wrong one more often than they
    make any other endpoint mistake. An aggregator reads. A publisher and an upload relay both
    write, but they differ in who holds the wallet and who pays.
- [Available Networks](https://docs.wal.app/docs/system-overview/available-networks.md):
    Walrus Mainnet operates a production-quality storage network using corresponding resources on
    the Sui Mainnet. The Walrus Testnet operates in conjunction with the Sui Testnet and is used to
    test new features before they graduate to Mainnet.
- [Caching](https://docs.wal.app/docs/system-overview/caching.md):
    Walrus blobs are content-addressed and immutable, which makes them well suited to caching. A
    given blob ID always maps to the same bytes, so once a response is cached it never goes stale
    for that blob ID.
- [Core Concepts](https://docs.wal.app/docs/system-overview/core-concepts.md):
    Walrus stores data as blobs. Each blob is an immutable array of byte
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Developer tools. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=docs.wal.app · GET /v1/domain/docs.wal.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for docs.wal.app:
1. POST https://agentwebmap.com/v1/sites/docs.wal.app/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://docs.wal.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/docs.wal.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/docs.wal.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.