# buying a tile

This is the entry point into the GitVerse RevShare economy. One transaction, 0.01 ETH, and you're in.

***

## Before you start

You need:

* A wallet (MetaMask, Rainbow, Coinbase, any injected wallet)
* Connected to **Base mainnet** (chainId 8453)
* **0.01 ETH** + a tiny bit for gas (\~0.0001 ETH usually)

If you're new to Base: bridge ETH from Ethereum mainnet via the [official Base bridge](https://bridge.base.org/), or buy directly on Coinbase and withdraw to Base network.

***

## The flow

1. Go to [gitverse.app](https://gitverse.app/) and open the **RevShare** tab.
2. Browse the grid. Cards labeled **AVAILABLE** are free to claim. Cards labeled **OWNED** belong to someone (you can still buy them — see [Buyout mechanics](broken://pages/134c3e4c1f9ad645aa292c34d73f31a1ac5b012f)).
3. Click any available card. The tile modal opens.
4. Click **Buy Planet · 0.01 ETH**.
5. Your wallet pops up. Confirm the transaction.
6. Wait \~2 seconds for confirmation on Base.
7. The modal updates: status flips to **OWNED**, owner becomes your address, owner actions appear.

That's it. You're a tile holder.

***

## What happens on-chain

Your transaction calls:

```
GitVersePlanets.claimTile(tileId, 0.01 ETH, repoName)
```

with `msg.value = 0.01 ETH`. The contract then:

1. Verifies the tile is empty and you don't already own 5 tiles.
2. Sends **0.007 ETH to the Treasury** (admission).
3. Sets your tile's **deposit to 0.003 ETH** (tax reserve).
4. Records your address as owner with declared price = 0.01 ETH.
5. Emits `TileClaimed` + `PlanetClaimed(tileId, you, repoName)` events.

The `repoName` is recorded in the event log, which is how the frontend reconstructs which repo each tile represents.

***

## What you get

The moment the transaction confirms:

* You appear as the owner on the RevShare grid.
* You start accruing your share of every new fee that enters the contract.
* You unlock the owner-only actions in the tile modal:
  * **Claim Fees** — withdraw accumulated holder share
  * **Add Deposit** — extend your tile's runway
  * **Set Price** — change your declared price
  * **Abandon Tile** — exit and recover your deposit

You also get **share/export rights** for the canonical planet image — the PNG export button on the planet detail page brands the image with your tile's identity.

***

## Limits

* **Maximum 5 tiles per wallet.** Enforced on every claim and every buyout.
* **Declared price must be ≥ 0.01 ETH.** This is the contract minimum.
* **You must send exactly 0.01 ETH** on `claimTile`. The contract reverts if you send more or less.
* **Total tiles = 10,000.** Once all are claimed (which is far away), no new claims are possible — you'd need to wait for someone to abandon or be foreclosed.

***

## Frequently confused

<details>

<summary>"If I'm sending 0.01 ETH and only 0.007 goes to Treasury, where does the rest go?"</summary>

The remaining 0.003 ETH stays inside your tile as the **tax deposit**. It's yours — used to pay weekly Harberger tax. Anything left when you abandon or get bought out comes back to you.

</details>

<details>

<summary>"Does the price I set affect the 0.01 ETH I pay to claim?"</summary>

No. The 0.01 ETH claim cost is fixed regardless of declared price. The declared price only affects future tax and buyout behavior.

</details>

<details>

<summary>"Can I claim someone else's repo as a tile?"</summary>

Yes. The contract doesn't validate repo ownership. Anyone can bind any repo name to any free tile. The point of `repoName` is to provide a human-readable label on the universe view — the gitlawb network is the source of truth for actual repo ownership.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitverse.gitbook.io/gitverse-docs/buying-a-tile.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.