# Calibration Rules

## .btc Name Calibration Rules

Some case including spaces,  "" is only used to show the full name clearly.

<table><thead><tr><th width="177">Scenes</th><th width="167">Case</th><th>Indexer View</th><th>Valid</th></tr></thead><tbody><tr><td>Default</td><td>"jack.btc"</td><td>jack.btc</td><td>✅</td></tr><tr><td>Capitalized initials</td><td>"Jack.btc"</td><td>jack.btc</td><td>✅</td></tr><tr><td>Capitalized name</td><td>"JACK.btc"</td><td>jack.btc</td><td>✅</td></tr><tr><td>All capital letters</td><td>"JACK.BTC"</td><td>jack.btc</td><td>✅</td></tr><tr><td>Uppercase suffix</td><td>"jack.BTC"</td><td>jack.btc</td><td>✅</td></tr><tr><td>Wide characters</td><td>"比特币.btc"</td><td>比特币.btc</td><td>✅</td></tr><tr><td>Emoji</td><td>"😀.btc"</td><td>😀.btc</td><td>✅</td></tr><tr><td>Multiple splits</td><td>"hi.jack.btc"</td><td></td><td>❌</td></tr><tr><td>First black</td><td>" jack.btc"</td><td></td><td>❌</td></tr><tr><td>Tail blank</td><td>"jack.btc "</td><td></td><td>❌</td></tr><tr><td>Middle blank</td><td>"hi jack.btc"</td><td></td><td>❌</td></tr><tr><td>First and last black</td><td>" jack.btc "</td><td></td><td>❌</td></tr><tr><td>Trailing line feed</td><td>"jack.btc\n"</td><td></td><td>❌</td></tr><tr><td>First line feed</td><td>"\njack.btc"</td><td></td><td>❌</td></tr><tr><td>Middle line feed</td><td>"hi\njack.btc"</td><td></td><td>❌</td></tr><tr><td>First and last line feed</td><td>"\njack.btc\n"</td><td></td><td>❌</td></tr><tr><td>JSON/JSON5</td><td><p>{</p><p> "p":"sns",</p><p> "op":"reg",    "name":"jack.btc"</p><p>}</p></td><td></td><td>❌</td></tr></tbody></table>


---

# 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-4-thinking-about-.btc-domain-name/calibration-rules.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.