Comment on page
Index Rules
- The ethscription content must be a valid Data URI starting with "data:"
- If the sha256 hash value of the UTF-8 content of the ethscription is repeated, later ethscribe ethscriptions are invalid.
ERC-20 uses the following fields to match（not available for erc-20 eths）
Deploy
Key | Required | Description |
|---|---|---|
p | yes | Protocol: erc-20, must be lowercase |
tick | yes | Ticker: symbol of ERC-20 in any size and case-insensitive, eg. ETCH = etch, max length: 18 |
op | yes | Operation: deploy |
max | yes | Max Supply: set max token supply, limited to uint256 |
lim | yes | Mint Limit: max amount can be minted per ordinal |
dec | no | Decimal: decimal precision must be <=18, default to 18 |
Mint
Key | Required | Description |
|---|---|---|
p | yes | Protocol: erc-20 must be lowercase |
tick | yes | Ticker: symbol of ERC-20 in any size and case-insensitive, eg. ETCH = etch, max length: 18 |
op | yes | Operation: mint |
id | yes | range: 1- max/lim |
amt | yes | mint amount , amt = lim, amt and lim must be equal |
Note: There cannot be any spaces or other special characters in the content of the token ethscription.
eths is an important token in the ethscription ecology, and the index adopts strong matching rules.
data:,{"p":"erc-20","op":"mint","tick":"eths","id":"1","amt":"1000"}
Last modified 3mo ago