AL 1.0 Alexandria Ordinal communications protocol GENESIS ordinal.
Alexandria, a protocol to define communication via bitcoin ordinals. Four message types are possible: New User, New Heading, New Post, New Mail and allow for communications services comparable to public chats, public posting sites and e-mail. Participants thereby own their usernames and messages.
Ordinals using this protocol start with the letters AL, followed by a semicolon, followed by two letters identifying the message type. Syntax of every message type is given below.
____________________________
New User Ordinal:
Message structure: AL;nU;user_name
user_name: Alphanumerical entry of arbitrary length (no hashtags, semicolons or backslash)
If one or more New User Ordinals exist with the same user_name, the New User ordinal with the lowest inscription number always remains valid.
____________________________
New Heading Ordinal:
Message structure: AL;nH;heading_code;heading_title
heading_code: one or many alphanumerical entries separated by a backslash, representing mainheading\subheading1\subheading2
heading_title: alphanumerical entry of arbitrary length representing the title of the new mainheading or subheading. New subheading1 can only be defined if the corresponding main heading already exists, new subheading2 only if the corresponding subheading1 already exists etc.. No semicolons, backslash or hashtags allowed.
If more than one New Heading ordinals with the same heading_code exist, the heading with the lowest inscription value always remains valid.
heading_codes are hierarchical, and every mainheading can have several subheading1, every subheading1 can have several subheading2 etc. The subheading code should be short.
____________________________
New Post Ordinal:
Message structure: AL;nP;user_name;heading_code;message_text
to be sent to the taproot address of the message sender. Funds for inscription must originate from corresponding SegWit address (intermediary transactions are allowed).
user_name: A user name, which has been previously defined by a New User ordinal.
heading_code: A heading code, which has been previously defined by a New Heading ordinal.
message_text: Message text of arbitrary length (within the limitations of ordinals inscriptions)
Post is only valid under this protocol and to be displayed by the frontend
IF the taproot address of the sender owns the nU ordinal of the corresponding user_name at the timepoint of posting
AND IF the heading_code has previously been defined with a New Heading ordinal.
AND IF the funds for the inscription originate from the SegWit address of the message sender.
The message text can include hashtags and links, but no semicolon or backslash.
The message text can include images or files by identifying the corresponding ordinal inscription numbers. These have to be lower than the inscription number of the New Post Ordinal.
_______________________________
New Mail Ordinal:
Message structure: AL;nM;subject_cyphertext;message_cyphertext
to be sent to the taproot address of the mail receiver.
subject_cyphertext: alphanumerical entry, which is the message subject encrypted with the public key of the message receiver. Should be short
message_cyphertext: alphanumerical entry, which is the message text encrypted with the public key of the message receiver. Limited in length by the text capacity of ordinals.
The messages can only be deciphered by the message receiver, using his private key.
________________________________________________
All types of AL type inscriptions can be traded, and with the constraints given above, the messages remain valid.
________________________________________________
Frontends can be programmed for the communication services according to this protocol, and frontend developers and suppliers may request service fees from users.
This protocol is CC BY, and attribution is to be given to Alice & Bob
________________________________________________
Discussion of this protocol is possible at the following heading: 1\1
Microblogging heading is 2\0 and allows text up to 280 characters. Use hashtags for categorization.