📬Operations

Documentation pertaining to the Operating Procedures for the Ordinals Mail Standard incorporating syntax for communications.

Ordinals Mail Standard

Sending Ordinals Mail is available to anyone that can transact on Bitcoin. Messages are inscribed as Ordinals and delivered to the recipient's BTC SegWit wallet address.

To send a message within the Ordinal Mail Standard, you can simply inscribe an ordinal containing the following syntax below.

Note: Please do NOT use line breaks within the "body" of your message; it may create JSON errors formatting the syntax.

Inscribing & Sending Mail

To send a message within the Ordinals Mail Standard, you can use the syntax provided below. This includes specifying the Ordinals Mail Standard protocol ("oms"), the operation ("send"), the sender and recipient's BTC SegWit addresses, the subject of the message, and the message body. You can find an example of the Ordinals Mail Standard by viewing Inscription #489493. However; it is recommended to write the body message in a single line without any line breaks, such as below:

{ 
"p": "oms",
"op": "send", 
"from": "segwit_address",
"to": "segwit_address",
"subject": "You got Mail Web3.0",

"body": "Hi, You Got Ordinals Mail!"
}

Key	Required?	Description
p	yes	Protocol: Helps future systems identify this as an Ordinals Mail Standard inscription
op	yes	Operation: send, reply
from	yes	Sender's btc segwit wallet address
to	yes	Receiver's btc segwit wallet address
subject	yes	Headline for the message
body	yes	Message

Replies

The Ordinals Mail Standard syntax also allows for reply functionality by changing the operation to "reply". The initial message being replied to can then be attached via additional syntax pulling the inscription on-chain.

{
"p": "oms",
"op": "reply",
"from": "segwit_address",
"to": "segwit_address",
"subject": "RE: You got Mail Web3.0",
  
"body": "Hi, Cool! Got it. Thanks for sending me Ordinals Mail!",
  
"data": [{
"title": "title_of_data",
"inscription": "inscription_id"
}]
}

Message + Attachments

Further more, the same on-chain syntax also allows for attachments to be included in messages by referencing the inscription ID of the attachment being referenced in the message.

{ 
"p": "oms",
"op": "send", 
"from": "segwit_address",
"to": "segwit_address",
"subject": "Ordinals Mail - see attached", 

"body": "Hi, Here's some details -xyz- about the attachment!",

"data": [{ 
"title": "title_of_data",
"inscription": "inscription_id"
}]
}

Experimental Syntax ⚠️ Sats Names

The Ordinals Mail Standard includes experimental syntax using Sats Names. This allows users to specify the owned unique name or alias for themselves and/or their recipients. This is obviously inspired by the popularity and potential utility uses of Sats Names within the Ordinals Protocol. You can find an example of the Ordinals Mail Standard with experimental Sats Names syntax by viewing Inscription #489459. However; it is recommended to write the body message in a single line without any line breaks, such as below:

{ 
"p": "oms",
"op": "send", 
"from": "segwit_address",
"from_alias": "sender.sats",
"to": "segwit_address",
"to_alias": "recipient.sats",
"subject": "You've got Mail Web 3.0",

"body": "Hi, You've Got Ordinals Mail!"
}

(inspired by Sats Names)

Key	Required?	Description
p	yes	Protocol: Helps future systems identify this as an Ordinals Mail Standard inscription
op	yes	Operation: send, reply
from	yes	Sender's btc segwit wallet address
from_alias	no	Sender's Sats Name alias
to	yes	Receiver's btc segwit wallet address
to_alias:	no	Receiver's Sats Name alias
subject	yes	Headline for the message
body	yes	Message

+ Group Threads

Additionally, the mention of group thread capability via Sats Names or ownerships of inscription's within "Collections" suggests that the Ordinals Mail Standard may standardize group messaging features in the future, which could be a useful feature for communication within the Ordinals ecosystem.