# Chapter 3：The Inspiration Source of BRC-20

After some time, around on February 20th, there was a person who came up with a whimsical idea of adding a string of JSON code to the domain name, creating a gimmick. They even created an official Twitter account, as shown in the image below, to promote this idea. The text containing the domain name was engraved as an inscription, and they changed the suffix to ".sats," with "sat" representing "satoshi." This form of adding code laid the foundation for the later development of BRC20 tokens. Due to the gimmick of adding code, several influential individuals started promoting it vigorously, and soon the .sats domain became widely known. There was even a person who inscribed over 2,000 4D.sats domains in one night. This form of adding code eventually inspired the inventor of BRC20 to launch the experimental project of creating tokens on the BTC blockchain.

Fun Fact:  .btc name(ordinals protocol) actually came before .sats with its earliest inscription at #18681

<div><figure><img src="https://3335534909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR65jfGtSN6XkteScE6NE%2Fuploads%2F7DamoIZHedymHaSccZbt%2F%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_20230626133743.jpg?alt=media&#x26;token=8e43bacc-613b-4a38-9d87-d3190eba5c33" alt=""><figcaption></figcaption></figure> <figure><img src="https://3335534909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR65jfGtSN6XkteScE6NE%2Fuploads%2FTKC5603vqWLL9qUgrBa3%2F%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_20230626133749.jpg?alt=media&#x26;token=0ea9b0b2-3d15-46a6-ab83-46c3a6a01c5b" alt=""><figcaption></figcaption></figure></div>


---

# 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://docs.btcname.id/docs/overview/chapter-3-the-inspiration-source-of-brc-20.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.