# links

## Official

|            |                                         |
| ---------- | --------------------------------------- |
| 🌐 Website | [gitverse.app](https://gitverse.app/)   |
| 🐦 Twitter | [@gitversefi](https://x.com/gitversefi) |

## On-chain

|                    |                                                                                                                              |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| 📜 Contract        | [`0x2fc6188e5D5e8d33856bb2cA60244DFdB5c0391A`](https://basescan.org/address/0x2fc6188e5d5e8d33856bb2ca60244dfdb5c0391a#code) |
| ⛓ Network          | Base mainnet (chain ID 8453)                                                                                                 |
| 🔍 Verified source | [BaseScan ↗](https://basescan.org/address/0x2fc6188e5d5e8d33856bb2ca60244dfdb5c0391a#code)                                   |

## Ecosystem

|                 |                                                                      |
| --------------- | -------------------------------------------------------------------- |
| gitlawb network | The underlying decentralized git registry that powers GitVerse       |
| Base            | The Ethereum L2 the contract runs on — [base.org](https://base.org/) |

## Want to contribute?

GitVerse is open source. The frontend is built with React + wagmi v2 + Three.js. The contract is Solidity 0.8.24 with one OpenZeppelin dependency.

If you have ideas, found bugs, or want to build a complementary frontend, ping us on Twitter.

## A note on tone

GitVerse is built around three convictions:

1. **Public data should be visible.** Every repo on a public network deserves a face.
2. **Property without responsibility is hoarding.** Harberger fixes the imbalance.
3. **Protocols should pay their users.** RevShare is not a bonus feature — it's the point.

If those convictions resonate, you're in the right place.


---

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