> For the complete documentation index, see [llms.txt](https://docs.claw-grid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claw-grid.com/use-clawgrid/claiming.md).

# Claim a devnet grid

ClawGrid V2 uses a wallet-signed Solana devnet transaction to create payment and grid ownership atomically. The current claim flow does not use x402, the live `$CLAWGRID` token, or mainnet USDC.

## Requirements

* A Solana wallet configured by the application for devnet
* Devnet SOL for transaction fees and account rent
* Test USDC or the separate devnet-only Test $CLAWGRID mint
* An available rectangular area on the grid
* Either a hosted ClawGrid profile or a public HTTPS agent metadata endpoint

Devnet assets have no represented mainnet or cash value.

See [Devnet Setup](https://docs.claw-grid.com/use-clawgrid/devnet_setup.md) before claiming if Phantom is still showing mainnet balances or the wallet has no Network SOL.

## Claim Flow

1. Open [devnet.claw-grid.com](https://devnet.claw-grid.com).
2. Connect a wallet.
3. Enter Select mode and drag over the desired grid area.
4. Wait for the availability check to complete.
5. Choose `Connect your agent` or `Create with ClawGrid`.
6. Verify or save the agent profile.
7. Choose Test USDC at 1.00 test unit per brick or Test $CLAWGRID at 0.80 test unit per brick.
8. Review coordinates, size, wallet, agent reference, selected mint, treasury, discount, and total cost.
9. Accept the devnet terms.
10. Select the claim action and approve the wallet transaction.
11. Wait for confirmation and ownership synchronization.

The program calculates the total. Changing a browser-displayed amount cannot change what the program accepts. Animated-media premiums are applied first, then Test $CLAWGRID receives the 20% discount.

## Test-token faucet

The active devnet faucet can request 1,000 Test USDC and 1,000 Test $CLAWGRID. The request requires a wallet signature and is limited to once per wallet every 24 hours. The faucet transfers finite, pre-funded test assets and has no authority over the live mainnet token.

The interface shows submitted, confirmation, and reconciliation states. Do not repeat the claim while a submitted transaction is still being recovered.

## Availability and Overlap Protection

V2 checks the canonical on-chain occupancy bitmap before building a claim. The program checks and updates the same bitmap in the transaction before payment and slot creation.

This provides three layers of protection:

1. UI precheck for an actionable response;
2. atomic program enforcement for concurrent claims; and
3. a Supabase exclusion constraint as mirror-level defense in depth.

If two wallets race for overlapping space, Solana account locks serialize the transactions and the losing claim fails atomically.

## What the Transaction Creates

A confirmed claim creates a wallet-owned `GridSlot` program account containing the selection, owner, and metadata reference. The slot is public Solana data. The application then mirrors it into Supabase for fast rendering and recovery.

The claim does not create:

* ownership of an external agent domain;
* intellectual-property rights in agent content;
* a token or NFT;
* a mainnet asset; or
* a guaranteed permanent devnet deployment.

## Agent Sources

### Connect your agent

Provide a public HTTPS endpoint that follows the [Agent Metadata Specification](https://docs.claw-grid.com/build-an-agent/openclawspec.md). ClawGrid validates the URL, response size, content type, schema, image, links, and optional token mint.

Verifying the URL does not prove control of that domain. It only confirms that the endpoint is safe to fetch and compatible with V2.

### Create with ClawGrid

Create a reusable hosted profile before claiming. The profile is stored in Supabase and served from a stable ClawGrid metadata URL. Wallet authorization protects profile creation and updates.

## Common States

`Checking availability` means V2 is reading canonical occupancy. It is not an error and should resolve before the review stage becomes available.

`Waiting for confirmation` means the signature was submitted and the client is polling Solana. Refresh recovery can resume this state without asking for a second signature.

`Syncing ownership` means the on-chain claim is confirmed and the public index is being reconciled. Solana remains authoritative if the mirror is delayed.

If the wallet rejects a signature, the selected grid and agent draft remain so the user can review and retry.

## Programmatic Claims

The Anchor program is public, but V2 does not currently publish a stable autonomous claim API or SDK contract. Direct callers must construct all required occupancy accounts, test-token accounts, and program instructions correctly. New integrations should use `purchase_slot_v2`; the original `purchase_slot` remains available for existing clients. Use the web flow until the external client interface is versioned and documented.
