# README

**A procedural universe of repositories — where every code project is a planet, every developer a star, and every protocol fee is shared with the holders.**

* [Live](https://gitverse.app/)
* [Twitter](https://x.com/gitversefi)
* [Network](https://basescan.org/address/0x2fc6188e5d5e8d33856bb2ca60244dfdb5c0391a)

## What is GitVerse?

GitVerse turns the gitlawb network — a public registry of open-source repositories — into an explorable 3D universe. Every repo becomes a unique planet, generated deterministically from its first commit hash. Two people in different cities see the same planet for the same repo. There is no hidden database: the universe is a pure formula over public network state.

On top of that, GitVerse runs an on-chain economy: **10,000 tiles**, each binding a planet to a Harberger-taxed property right. Owning a tile gives you a share of every fee that flows through the protocol — buyouts, appreciation taxes, weekly land tax, and any future token revenue.

## What can I do here?

| Action                          | Where                                                                                      |
| ------------------------------- | ------------------------------------------------------------------------------------------ |
| Browse the universe in 2D or 3D | [gitverse.app](https://gitverse.app/)                                                      |
| Buy a planet tile (0.01 ETH)    | RevShare page on the app                                                                   |
| Earn protocol revenue           | Automatic for tile holders                                                                 |
| Buy a tile from another holder  | Harberger buyout — any time                                                                |
| Read the contract source        | [BaseScan ↗](https://basescan.org/address/0x2fc6188e5d5e8d33856bb2ca60244dfdb5c0391a#code) |

## Start here

* 👉 [Introduction](broken://pages/8b776e700ab031f9fe5e7107c3f936280f85df98) — the elevator pitch
* 👉 [How it works](broken://pages/d1fd3bd762c622f97e2166922e34bb1d125d537a) — universe + economy in one page
* 👉 [RevShare Overview](broken://pages/85820c2cd86b66ef1253db0331af3a2f37bbe218) — the revenue-sharing mechanic
* 👉 [Buying a Tile](broken://pages/10387612bca9377460d2147a16e9bc78580bc7a1) — your first transaction
* 👉 [FAQ](broken://pages/c4d2855464b72a936a07225ad4c7c27633f8eac5) — quick answers

## Links

* 🌐 Website: [gitverse.app](https://gitverse.app/)
* 🐦 Twitter: [@gitversefi](https://x.com/gitversefi)
* 📜 Contract on Base: [`0x2fc6188e5D5e8d33856bb2cA60244DFdB5c0391A`](https://basescan.org/address/0x2fc6188e5d5e8d33856bb2ca60244dfdb5c0391a#code)


---

# 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/readme.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.