> For the complete documentation index, see [llms.txt](https://docs.bellsight.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bellsight.xyz/bellsight/bellsight-sns-api/about.md).

# About

The Sats Names System (SNS) is now being adopted by Bellsight with a few simplifications from Bitcoin to Bellscoin, marking a significant evolution in our journey. Initially established as a standard for writing names to Bitcoin using ordinals, SNS aimed to build a robust name ecosystem created by Bitcoiners and developed entirely on Bitcoin. Early adopters began inscribing .ord and .btc names with ordinals, leading to the formalization of the SNS process. This introduced the first JSON protocol on Bitcoin and the .sats namespace, which has since seen widespread adoption and inspired a proliferation of namespaces and JSON meta-protocols on Bitcoin.

Now, as SNS transitions to Bellscoin, the guiding principles remain intact:

* **All namestate lives on Bellscoin**: Bellscoin transactions, and only Bellscoin transactions, are necessary to register and update names. A Bellscoin node will contain all the information needed to materialize all namestate, ensuring no other database or trusted services are required. Any client can independently compute the true state of all names.
* **The standard will remain credibly neutral**: There are no gatekeepers; nobody can disable the standard or block anyone from registering names. There is no smart contract or front end with privileged access. No tokenomics, no premine, no gas token, no governance, and no perverse incentives are involved.
* **The first write of a name on Bellscoin owns the name**: For example, the first user to register an ordinal containing "satoshi.sats" on Bellscoin owns that name and the rights to update it. With ordinals, anyone can write any data they wish, including duplicate names. This may lead to collisions and competing name standards, but bickering over various standards is counterproductive. The only neutral, objective way to settle these collisions is the "first is first" principle.

As SNS integrates with Bellscoin, we continue to uphold these principles to maintain the integrity and neutrality of the name ecosystem.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.bellsight.xyz/bellsight/bellsight-sns-api/about.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
