erc-20
ERC-20 is a fully community-driven experimental standard. Take part in the experiment at your own risk.
There are several erc-20 tokens appearing in Ethscriptions like $eths, $gwei and $ercs, but no one has defined the erc-20 token standard in Ethscriptions. Instead, different people deployed and minted those tokens, and other people writed indexers of erc-20 tokens. So far, the usual community indexers of erc-20 tokens are consistent and work properly. So this doc is written to describe the community-driven experimental erc-20 token standard in Ethscriptions simply.
Introducing Ethscriptions Ethscriptions are a new way of creating and sharing digital artifacts on Ethereum using transaction calldata. You can learn about ethscriptions with following resources: Offical website: OKX learn:
Concept of ERC-20 Deploy new ERC-20 tokens with deploy events Mint ERC-20 tokens with mint events Transfer ERC-20 tokens with transfer events
Operations 3.1 Operation: Deploy The deploy operation will deploy a ERC-20 token. Name Key Requried Description Protocol p yes helps other systems identify and process erc-20 events Operation op yes type of event (Deploy, Mint, Transfer) Ticker tick yes the case insensitive identifier of erc-20 Max supply max yes set max supply of the erc-20 Mint limit lim yes set max amount that can be minted per ethscription
Deploy Example: line 3.1.1: data:,{"p":"erc-20","op":"deploy","tick":"eths","max":"21000000","lim":"1000"} Line 3.1.1 will deploy a ERC-20 token $eths with max supply of 21,000,000 and limit 1000 per mint. line 3.1.2: data:,{"p":"erc-20","op":"deploy","tick":"TICKER_NAME","max":"MAX_SUPPLY","lim":"MINT_LIMIT"}
Line 3.1.2 will deploy a ERC-20 token $TICKER_NAME with max supply of MAX_SUPPLY and limit MINT_LIMIT per mint.
To deploy a specific ERC-20 token, just copy line 3.1.2 and replace TICKER_NAME, MAX_SUPPLY and MINT_LIMITwith real values.
3.2 Operation: Mint The mint operation will mint ERC-20 tokens if the ERC-20 token is deployed. Name Key Requried Description Protocol p yes helps other systems identify and process erc-20 events Operation op yes type of event (Deploy, Mint, Transfer) Ticker tick yes the case insensitive identifier of erc-20 Identifier id yes the unique identifier of the erc-20 ethscription Amount to mint amt yes state the amount of the brc-20 to mint, less than "lim" above if stated
Mint Example: line 3.2.1: data:,{"p":"erc-20","op":"mint","tick":"eths","id":"1","amt":"1000"} Line 3.2.1 will mint 1000 ERC-20 tokens $eths and the unique erc-20 ethscription identifier is "1". line 3.2.2: data:,{"p":"erc-20","op":"mint","tick":"TICKER_NAME","id":"IDENTIFIER","amt":"MINT_AMOUNT"}
Line 3.2.2 will mint MINT_AMOUNT ERC-20 tokens $TICKER_NAME and the unique erc-20 ethscription identifier is IDENTIFIER.
To mint specific ERC-20 tokens, just copy line 3.2.2 and replace TICKER_NAME, IDENTIFIER and MINT_AMOUNT with real values.
3.3 Operation: Transfer Currently, the community is using the transfer function of ethscriptions to transfer erc-20. The transfer operation remains to be developed.