> For the complete documentation index, see [llms.txt](https://nibiru.kevinyang.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nibiru.kevinyang.dev/introduction.md).

# Introduction

{% hint style="info" %}
**About the author**

Hi, my name is Kevin Yang and I am the CTO and co-founder of Nibiru Chain. Previously, I was a software engineer at Google and an engineering student at the University of Waterloo.\
\
Twitter: <https://twitter.com/ShanghaiYang>

LinkedIn: <https://www.linkedin.com/in/kyang95/>

Instagram: <https://www.instagram.com/mrkevinyang>
{% endhint %}

## About this site

This site is my personal knowledge book for working with Nibiru Chain. You should read the [official docs](https://nibiru.fi/docs) also. You may ask why I made a separate site when the official docs already exist? There are a couple of reasons:

1. The official docs is targeted at a broader audience, such as web3 beginners, investors, developers, blockchain users, and infra operators/validators. This site is focused primarily on developers.
2. This site allows me to iterate quickly without having to worry about SEO or branding. That being said, all content on this site is completely independent and not representative of the Nibiru Chain foundation.

## Navigating the site

The site's structure is based off [Divio's "four types of documentation"](https://docs.divio.com/documentation-system/):&#x20;

* tutorials
* how-to guides
* technical reference
* explanation

Each type of documentation has its own section in the navigation.&#x20;

**Tutorials** are zero-to-hero follow along guides that assume zero prior knowledge

**How-to guides** are quick and easy scripts and steps that accomplish one specific thing.

**References** are full specifications of a specific sub-system.

**Explanations** are written to develop a conceptual understanding.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://nibiru.kevinyang.dev/introduction.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.