# Introduction

<figure><img src="https://3735057740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0S74HiGVG9aq0Jpi6Ozh%2Fuploads%2F7vo0nLUBbaSlZ1pZjhmO%2FMy%20project-1.png?alt=media&#x26;token=f7b2e77d-0d5b-4e8b-bcb9-00ff10376337" alt=""><figcaption></figcaption></figure>

### HOW IT STARTED

It started with a now infamous [tweet](https://twitter.com/domodata/status/1633658974686855168?s=20). BRC-20 launched as a fun experiment standard for tokens on bitcoin. The goal was to encourage the bitcoin community to play around with and optimize the standard until a general consenses on best practices could be agreed upon, or to decide if the standard was a waste of time.&#x20;

### BRC-20 FUNCTIONALITY

These functions together allow for a simple yet effective way for users to deploy, buy, and sell tokens.&#x20;

* Create a brc-20 'token' with the deploy function
* Mint an amount of brc-20's with the mint function
* Transfer an amount of brc-20's with the transfer function

### WHERE IT'S GOING

No body really knows where this could take us. The experiment has grown and continues to grow at a rapid speed. The bitcoin memepool is so full and transactions are getting backlogged by the hundreds if not thousands. Developers are building features for the users, and although primitive at the moment becoming far easier to understand and much more intuitive. As developers continue to build and features become easier to use. Who knows what might happen next.&#x20;


---

# 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://www.brc20.guide/getting-started/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.
