# About

### Introduction

<img src="/files/51GnixlLbWGS6tiL6sbZ" alt="OrdinalsMail" data-size="line"> Ordinals Mail Standard. Web 3.0

An analysis of on-chain Ordinals Inscriptions thus far reveal the use of various *Multipurpose Internet **Mail** Extensions* or *MIME* content types; however, the *primary* MIME subtype **Message/RFC822** has been not yet been standardized. Therefore; it is our mission to integrate Mail into the Ordinals ecosystem and establish the **Ordinals Mail Standard** that will facilitate the development of future Web 3 communications and applications.

#### <img src="/files/M5JRw3wRlAG39ltj7ReG" alt="Ordinal Mail" data-size="line"> Goal

Our goal is to establish the *Ordinals Mail Standard* via syntax by deriving it from the *RFC822 subtype* format. This standard will enable messaging between Bitcoin Blockchain users through the Ordinals Protocol.&#x20;

<img src="/files/K1XmDW1zGMbqEDlVYXCf" alt="Ordinals Mail" data-size="line"> **Plan**

**Ordinals Mail** will be among the first Ordinals Standards to adopt *Sats Names*, providing an ideal use case for this experimental syntax naming convention for both the sender and recipient wallet addresses.&#x20;

![Ordinals Mail Standard](/files/6Uy2HKUlpKu0gt90YInR)

#### Decentralized Web 3 Communication

* [<mark style="color:green;">**Ordinals Mail**</mark>](https://ordinalsmail.com)
* ~~<mark style="color:red;">GMAIL</mark>~~
* ~~<mark style="color:yellow;">Yahoo Mail</mark>~~
* ~~<mark style="color:orange;">AOL Mail</mark>~~


---

# 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.ordinalsmail.com/about.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.