⚠️ Experiments

STOP! these are experimental playground ideas for stuff not related to esc-20. browse at your own risk. and don't use any of it in production.

Potential Ethscription Name Service Format

Here's a JSON representation of how a 'proper' Ethscription Name Service protocol might look like:

{
  "p": "esns",
  "op": "reg",
  "name": "rekt",
  "sfx": "eths"
}

Which would render as rekt.eths when ethscribed like this:

data:application/json,{"p":"esns","op":"reg","name":"rekt","sfx":"eths"}

Name	Key	Required	Description
Protocol	p	yes	Protocol: "esns" for Ethscription Name Service.
Operation	op	yes	Specifies the operation being performed on the Ethscriptions Name Service. In this case, "reg" indicates a registration operation, meaning that you are attempting to register a new Ethscription.
Name	name	yes	Refers to the desired name for the Ethscription. This name will be combined with the suffix to form the complete Ethscription render.
Suffix	sfx	yes	Represents the suffix for the Ethscription, like eths or eth or even ethmap or e.

Additional operations might be: associate content, update content, delete content, etc

ESC-20 Transfer Receipts

Step 2: Transfer Event Receipt??

The sender can share the transfer event details with the recipient as a receipt. This can be done by sending the transfer event inscription to the recipient after providing the necessary details such as the transfer transaction hash.

The recipient should receive the transfer event receipt and confirm the transfer by inspecting the provided details. They can verify the sender's address, the token ticker symbol, and the transferred amount to ensure the accuracy of the transfer for their own records, HOWEVER,