# AtBitcoin Protocol Whitepaper

### Abstract

@bitcoin is a simple, permanent naming system built natively on Bitcoin. It uses the Ordinals protocol's **parent‑child provenance** feature to create verifiable, human‑readable handles (e.g., `satoshi@bitcoin`) that are owned by users forever. No renewal fees. No centralized control. Just Bitcoin.

***

### 1. Introduction

Bitcoin addresses are long, confusing, and impossible to remember. Social media usernames are rented, not owned. Decentralized identity solutions often require separate blockchains or complex smart contracts.

@bitcoin solves this by creating a naming layer directly on Bitcoin Layer 1. Each handle is an Ordinal inscription—a digital artifact permanently stored on the world's most secure blockchain.

The root of the system is a single parent inscription: **`@bitcoin`**. Every registered handle is a child of this parent, creating an unbreakable chain of authenticity.

***

### 2. How It Works

#### 2.1 The Parent Inscription

The protocol begins with one inscription containing the text `@bitcoin`. This is the **root**. Its unique Inscription ID serves as the permanent anchor for all official handles.

**Official Parent Inscription ID:**\
`0fab1698c19656e547d13a740f8040e4edfbbd04b814a4ec0aff4793b535206ei0`

#### 2.2 Child Inscriptions

When a user claims a handle (e.g., `alice`), a new inscription is created containing the text `alice@bitcoin`. This inscription is created as a **child** of the `@bitcoin` parent.

The parent‑child relationship is verified on‑chain using Bitcoin's UTXO model and the Ordinals protocol's provenance rules. The transaction that creates the child must spend the UTXO holding the parent inscription and include a `tag3` metadata field with the parent's ID. Any Ordinals explorer can confirm that `alice@bitcoin` is an authentic child of the official `@bitcoin` parent.

#### 2.3 The Official Directory

All registered handles are recorded in a public, read‑only directory. This directory is manually maintained by the protocol operator but is verifiable against on‑chain data. Anyone can view which Bitcoin address owns which handle and track the status of their registration.

***

### 3. Why @bitcoin Matters

| Problem                                                | @bitcoin Solution                                     |
| ------------------------------------------------------ | ----------------------------------------------------- |
| Bitcoin addresses are long and error‑prone (`bc1q...`) | Send Bitcoin to `alice@bitcoin` instead               |
| Usernames on centralized platforms can be deleted      | Handles are inscribed on Bitcoin and cannot be erased |
| No way to prove ownership of a name across platforms   | Parent‑child link proves authenticity on‑chain        |
| ENS requires Ethereum and annual renewal fees          | @bitcoin lives on Bitcoin L1 with no renewal fees     |

***

### 4. Use Cases

#### 4.1 Simplified Bitcoin Payments

Instead of sharing a long Bitcoin address, users can share their handle. Wallets and services that integrate @bitcoin can resolve `alice@bitcoin` to the correct address automatically.

#### 4.2 Decentralized Identity

A handle serves as a portable, self‑custodied digital identity. Users can sign messages with their inscription's private key to prove they own `alice@bitcoin` anywhere on the web.

#### 4.3 Community Membership

Exclusive communities can gate access based on handle ownership. Holding `member@bitcoin` could unlock private chats, content, or events.

#### 4.4 Digital Collectible

Each handle is a unique Ordinal inscription. Early handles on a historic parent like `@bitcoin` may hold collectible value.

***

### 5. Handle Lifecycle

#### 5.1 Registration

1. User checks availability via the @bitcoin website or the official directory.
2. User submits a registration request with their desired handle and Bitcoin address.
3. User receives payment instructions and sends exactly **0.0002 BTC** to the protocol address.
4. User submits their transaction ID (TXID) for verification.
5. The protocol operator verifies the payment, then manually inscribes the handle as a child of `@bitcoin`.
6. The inscription is transferred to the user's Bitcoin address.

#### 5.2 Status Workflow

| Status            | Meaning                                      |
| ----------------- | -------------------------------------------- |
| `WAITING_PAYMENT` | Request submitted, awaiting payment          |
| `VERIFYING`       | Payment TXID received, awaiting confirmation |
| `INSCRIBED`       | Child inscription created on‑chain           |
| `COMPLETED`       | Inscription transferred to user              |

Users can track their handle's status in the public directory. Once the status shows `INSCRIBED` and an Inscription ID appears, the handle is live.

#### 5.3 Ownership

Once inscribed, the handle is a standard Ordinal. The owner can:

* Hold it in any compatible wallet (Xverse, Leather, UniSat)
* Transfer it to another Bitcoin address
* Use it as their permanent Bitcoin identity

#### 5.4 Updates

To update the Bitcoin address associated with a handle, the owner can request a new child inscription. The directory will point to the most recent entry.

#### 5.5 Transfer

Handles can be sent like any other Bitcoin asset. The new owner gains full control of the identity.

***

### 6. Comparison to Other Systems

| Feature          | AtBitcoin             | ENS                     | Spaces Protocol     |
| ---------------- | --------------------- | ----------------------- | ------------------- |
| Blockchain       | Bitcoin L1            | Ethereum                | Bitcoin + Off‑Chain |
| Fully On‑Chain   | Yes                   | Yes (contract state)    | Partial             |
| Renewal Fees     | None                  | Yes (annual)            | None                |
| Simplicity       | High                  | Medium                  | Complex             |
| Permanent Record | Yes (inscription)     | No                      | Partial             |
| Trust Model      | Bitcoin Proof‑of‑Work | Ethereum Proof‑of‑Stake | Hybrid              |

***

### 7. Technical Foundation

@bitcoin is built on the **Ordinals protocol**, specifically leveraging **Parent‑Child Provenance**.

* **Parent Inscription ID**: `0fab1698c19656e547d13a740f8040e4edfbbd04b814a4ec0aff4793b535206ei0`
* **Child Inscription**: Created using a Bitcoin transaction that spends the parent UTXO and includes the parent ID in a `tag3` metadata field.
* **Verification**: Any Ordinals indexer (ord server, ordinals.com) can validate the parent‑child link.

This standard is open, auditable, and already supported by major Bitcoin wallets and explorers.

***

### 8. The @bitcoin Directory

The protocol maintains a public, read‑only directory of all registered handles. This directory is:

* **Verifiable**: Data can be cross‑checked against on‑chain inscriptions.
* **Transparent**: Anyone can audit the list of handles and their owners.
* **Accessible**: Available as a simple web view for users.

Example directory entry:

| Handle         | Bitcoin Address | Status    | Inscription ID |
| -------------- | --------------- | --------- | -------------- |
| alice\@bitcoin | bc1qxy...       | COMPLETED | abc123...i0    |
| bob\@bitcoin   | bc1qab...       | INSCRIBED | def456...i1    |

***

### 9. Fee Structure

@bitcoin charges a **one‑time registration fee** of **0.0002 BTC** per handle. This fee covers:

* Bitcoin network transaction costs (inscription + transfer)
* Operational overhead of manual processing
* Protocol maintenance and future development

There are **no recurring fees**. Once registered, a handle belongs to its owner forever.

*Note: The BTC amount is fixed; USD equivalent varies with market price.*

***

### 10. Security & Trust

#### 10.1 Self‑Custody

Handles are held in the user's own Bitcoin wallet. @bitcoin never takes custody of user funds or inscriptions.

#### 10.2 Immutability

Once inscribed, a handle cannot be altered or deleted. The record is permanent on the Bitcoin blockchain.

#### 10.3 Verifiability

The parent‑child link can be independently verified by anyone running an Ordinals node or using a public explorer. No trust in the protocol operator is required.

***

### 11. Roadmap

#### Phase 1: Foundation (Current)

* Inscribe the `@bitcoin` parent
* Launch manual registration via website
* Publish public directory

#### Phase 2: Automation

* Automate payment verification
* Build simple resolution API for wallets

#### Phase 3: Integration

* Partner with Ordinals wallets for native handle display
* Enable handle‑based Bitcoin payments

#### Phase 4: Community Governance

* Explore decentralized management of the protocol
* Introduce handle auctions for premium names

***

### 12. Frequently Asked Questions

#### Q: What is an @bitcoin handle?

A: A human‑readable name (e.g., `alice@bitcoin`) inscribed permanently on Bitcoin. It can be used as an alias for a Bitcoin address or as a digital identity.

#### Q: How do I get a handle?

A: Visit the @bitcoin website, check availability, submit a request, send 0.0002 BTC, and confirm your TXID. The handle will be inscribed and sent to your Bitcoin wallet.

#### Q: How much does it cost?

A: A one‑time registration fee of **0.0002 BTC**. No renewal fees.

#### Q: Is there a renewal fee?

A: No. Once inscribed, the handle is yours forever.

#### Q: Can I transfer my handle?

A: Yes. It is a standard Ordinal inscription. Send it to any Bitcoin address using a compatible wallet.

#### Q: What wallets support @bitcoin handles?

A: Any wallet that supports Ordinals, including Xverse, Leather, and UniSat.

#### Q: How can I verify a handle is authentic?

A: Check the parent‑child link on any Ordinals explorer. The handle should be listed as a child of the official `@bitcoin` parent inscription.

#### Q: What happens if I lose access to my wallet?

A: Like any self‑custodied Bitcoin asset, losing your private key means losing access to the handle. Keep your seed phrase safe.

#### Q: Can I point my handle to a new Bitcoin address later?

A: Yes. Request an update inscription. The directory will reflect the most recent entry.

***

### 13. Conclusion

@bitcoin brings simple, permanent identities to Bitcoin. By leveraging Ordinals parent‑child provenance, it creates a naming system that is verifiable, immutable, and owned by users—not platforms.

In a digital world where identity is increasingly fragmented and controlled by corporations, @bitcoin offers a sovereign alternative: a name you truly own, forever recorded on the world's most secure ledger.

***

**Claim your handle. Own your identity. @bitcoin**