> For the complete documentation index, see [llms.txt](https://bitcoinnative.gitbook.io/at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bitcoinnative.gitbook.io/at/bitcoin-at-protocol-a-bitcoin-networks-account-system.md).

# "Bitcoin @AT Protocol" ：A Bitcoin network's @ account system

crypto native ≠ bitcoin native.

## Introduction

The name of this proposal originates from the pronunciation of the '@' symbol. '@account' is the most widely used username format on the Internet, with a vast user consensus globally. If the @account format also becomes popular and adopted in the Bitcoin ecosystem, it can greatly reduce the learning curve for new users and minimize the differences in usage habits. The Bitcoin AT Protocol aims to introduce an @account system to the Bitcoin network while adhering to the original design principles of Bitcoin.

![](https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2F1Hk4zE20upYDyxZqQYDR%2Fimage.png?alt=media\&token=efa86fb4-eb45-4902-b5c0-85a6d9659745)![](https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2FQS720vIjn6kXIV5IhWXz%2Fimage.png?alt=media\&token=47d52a5c-4253-4166-8d3f-1d6b7fcb3156)

![](https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2FW9XysFtZKaHCYbq5e7rp%2Fimage.png?alt=media\&token=97c37b4c-c249-4633-a628-1922d1b4fb61)![](https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2FTzvuqFAkz43P4MiwiYT4%2Fimage.png?alt=media\&token=c23d208d-22a1-4b10-96ed-2102e882032b)

As shown in the above figure, these well-known products with a large user base all use the @account format, instead of the domain suffix pattern like bitcoin.paypal, bitcoin.telegram, bitcoin.twitter. This is because @account is the native account format, and they do not need to add a domain suffix to emphasize their application scenarios.

**Similarly, "Crypto native" and "Bitcoin native" are two cultural attributes and** **technical attributes that are not entirely the same.**&#x20;

With the development of concepts such as Lightning Network, DID, etc., the emergence of products like Nostr has shown us even greater possibilities for the Bitcoin ecosystem thus we can expect an even wider range of account applications and usage in the future of the Bitcoin network ecosystem.

&#x20;

Perhaps one day we will no longer need centralized social media platforms like Twitter. The way we greet new friends will change from "Hi, what's your Twitter account?" to "Hi, what's your Bitcoin account?" At that time, you can directly tell your friends, "Hi, this is my Bitcoin account.”

![](https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2FPUlAmDPWbTGP3kt3h7Q0%2Fimage.png?alt=media\&token=15968eaa-9017-444f-b408-20baf5e8c6b4)

At that time, there will be no need to emphasize the suffix, and the whole process will be as simple and natural as a web 2.0 account. Therefore, it is time to propose a protocol standard that allows Bitcoin users to have this type of account format.

## Protocol Design Principles

One of the original intentions of Bitcoin was to create a more inclusive and trustworthy financial system, making it easier for people who are excluded from the traditional financial system to access it. Thanks to the Bitcoin community's adherence to the original intention of Bitcoin and the Satoshi Nakamoto's vision, Bitcoin has been moving in this direction since its inception. Therefore, the design of the ***Bitcoin AT protocol specification should also embody the concepts of inclusiveness, user-friendliness, and scalability.***

### **Bitcoin Native Principles**

The registration and update process for all accounts are completed on the Bitcoin mainnet. Registration follows the principle of "first come, first served" based on Bitcoin block transaction confirmation. Everyone can independently read the account status, and no third party can deprive others of the right to register, manage, and own the account.

### ***Compatibility***

The protocol design of AT accounts will not conflict with existing protocols, such as the protocols for web 2.0 and web 3.0 domains.

### **User-friendliness**

&#x20;The account registration process should follow the principle of no-code as much as possible. The best design is the one that every user can understand and use at the first time.

### **Scalability**

&#x20;To face the infinite possibilities of future application scenarios, the design should be scalable. Therefore, the option to create sub-accounts should be retained when creating a main account.

&#x20;

## **Quick Start**

&#x20;Following the above principles, registering a new account only requires creating a plain text format Ordinals that meets the format requirements.

What are Ordinals: <https://docs.ordinals.com/inscriptions.html>

### Format Standard

The account can only start with the "@" symbol, and the main account can only contain one "@" symbol.

* The account can only start with the "@" symbol, and the main account can only contain one "@" symbol.
* "Space", "." and "/" symbols are not allowed in the account.
* Only the main account can create sub-accounts in the format of “@mainaccount\@sub-account".
* Any UTF-8 character is valid.
* Capitalization is not important, and all accounts will be registered as lowercase.
* Each Ordinals can only inscribe one account.

Account registration [example](https://ordinals.com/inscription/5b07c18b8873235c0ce062061fc0dfb0dcd7ea1de1440e1ab96f6241d9f7742ai0)

<figure><img src="https://3965500662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FURDk8xyoV6izAkObkKxB%2Fuploads%2FSnevlyhqd3hhTxr2APg4%2Fimage.png?alt=media&amp;token=2cf613f7-dfe8-4c5b-9c4b-193830e1f3dd" alt="" width="375"><figcaption></figcaption></figure>

## Building an Indexer

These instructions explain the logic for extracting and validating @accounts so that they can be properly indexed and determine when each @account was first registered.

### 1.Retrieving Data

The following instructions are based on the assumption that the entire Ordinals data structure can be accessed, including basic details such as type, ID, and text content.&#x20;

The principle of "first come, first served" must be followed, and indexing must start from Inscription Number 1.

To follow the principle of no-code as much as possible, verify that the type of the inscription is:

`text/plain`

Retrieve “text” as the original text content of the inscription

&#x20;Account Example: [Retrieve Original Data](https://ordinals.com/inscription/5b07c18b8873235c0ce062061fc0dfb0dcd7ea1de1440e1ab96f6241d9f7742ai0)

### 2. Verify the main account

&#x20;

The first inscribed @account number is the only valid one in the system, so it is necessary to determine the account ownership by judging the order of the inscription numbers.

* Verify that the account number does not contain periods (.) and (/).
* Deletes everything after the first space or newline (\n).
* Removes all whitespace and newlines.
* Verify that the string starts with @ and has only one @ symbol.
* Convert a string to lowercase.

### 3. Verify the sub-account

&#x20;

In order to maintain the order of the system, only sub-accounts that generated under the authorization of the main account are valid accounts.

Account format: " @mainaccount\@sub-account “

Due to the lack of applications in the current Bitcoin network, it is currently not recommended to use this function. The community can decide whether to enable this function according to the situation.

**Remark:**

&#x20;

1\. The parser should ensure that the API returns a decoded UTF-8 domain name, so that users can identify the hidden characters in the account by identifying this information.

2\.  This agreement is only at a proposal stage. Please decide whether to use this standard under the premise of complying with the laws of your region. The proposal itself does not have any expectation of return on investment.

3.Copyright

This work is placed in the public domain.

References

\[1] Satoshi, "Bitcoin: A Peer-to-Peer Electronic Cash System," <https://bitcoin.org/bitcoin.pdf>

\[2] Casey Rodarmor , "Ordinal Theory Handbook,"  <https://docs.ordinals.com/inscriptions.html>

\[3] Sats Names , "The first JSON protocol," <https://docs.sats.id/sats-names/about>
