AbaRC-20 Token Protocol on Aba Blockchain

AbaRC-20 is a token protocol built on top of the Abordinals on-chain NFT standard and the CHIP-7 standard, which are in turn built on the NFT1/NFT0 standards. AbaRC-20 is influenced by BRC-20 on Bitcoin, but benefits from NFT1, Offer files and other capabilities of the Aba blockchain.

AbaRC-20 tickers ("tick") are unique and case-insensitive. The first valid deploy command on the Aba blockchain for a ticker specifies the parameters for said ticker. For example, there can only be one "MOJOS" ticker deploy command. Subsequent

This standard specifies values and fields in different parts of the NFT1 standard. Example files and scripts are included in a public git repo. This standard has been designed with the aim of supporting easy indexing and support by existing ecosystem projects, as well as easy validation where possible. While the BRC-20 standard on Bitcoin only uses the "uri" equivalent for Aba NFT's, the AbaRC-20 standard also specifies values for other fields in the NFT1 & CHIP-0007 standards. When in doubt, refer to the code samples.

Differences from BRC-20 include:

Immediately tradeable through existing blockchain trading infrastructure
Multilingual characters supported in the ticker
Wider length of ticker symbols supported
MaxBlock option makes verification of valid mints easier
Optionality of "lim" field in mint commands simplifies minting
Extended fields for logos and links in deploy command helps community development

Design Choices

As with Abordinals, part of the aim is to be easily integrated by the rest of ecosystem
Aim to be easily parsed, with standard JSON
Consideration given to presentation & viewing
Connect to the heritage of the BRC-20 standard to encourage new adoption and attention from beyond the existing user base
"If we didn't do it, someone else would" (but perhaps w/ worse design than this)

Get Notifications of Updates

Get updates from creator Anarkoic on new releases, airdrops, etc.

Tokens List on Chordifun

AbaRC-20 tools on Github

Commands

The two "commands" for AbaRC-20 are "Deploy" and "Mint". Note that a valid Mint command NFT is also the tradeable AbaRC-20 token itself.

Only one AbaRC-20 command may be issued in a Abordinal. The AbaRC-20 doesn't need to be minted using a DID. Minting without a DID has a lower clvm cost, and takes up less space. To mint without DID's make sure you use the wallet id of a regular NFT wallet id (see "chia wallet show") inside your Aba wallet. You may wish to mint AbaRC-20 Deploy commands with a DID though for historical significance and provenance. The Deploy NFT may have historical value to some, and thus an independent value of its own.

For this initial version, AbaRC-20 Abordinals must be base64-encoded json files of media type application/json (preferably) or plain/text. This helps apps integrating them index / verify easily.

Deploy

Deploy opens minting for a particular ticker, with minting being permitted starting in the following block after the block that the Deploy NFT is minted in. Supply can be specified either by a maximum minting block number or a maximum number of tokens.

See sample files in the abarc-20 git repository

Requirements:

CHIP-7 Abordinal
A Deploy command may have a royalty
CHIP-7 Name field must be ticker ("tick", e.g. "abordi"), followed by a space and "deploy", e.g. "abordi deploy"
CHIP-7 Description field of the NFT must be "abarc-20 deploy"
one and one only of "maxBlock" integer or "max" (integer) must be included
If using "max", the amount must be a positive integer.
If using "maxBlock", the Aba block number must also be greater than 6,334,414 & also greater than the # of the block the deploy command Abordinal is in

Only one command may be issued in a Abordinal.

URI content Outline:

 {
  "p": "abarc-20",
  "op": "deploy",
  "tick": "abordi",
  "maxBlock": "6400000",
  "lim": "100",
  "description": "",
  "logos": ["https://www.abarc20.com/abordi/abordi.png", "https://www.abordinals.com/abordi/abordi.png", "https://www.abarc20.com/abordi/abordi.mp4", "https://www.abordinals.com/abordi/abordi.mp4"],
  "links": ["https://www.abarc20.com/abordi/", "https://x.com/abordinals", "https://discord.gg/TGddbKbEp4", "https://www.abordinals.com/abordi/"],
  "v": "1" # version, optional, default value is 1,
  "t": # optional, reserved for future use,
  "data": # optional, can be used for extensions
}

URI content Example:

{
  "p": "abarc-20",
  "op": "deploy",
  "tick": "abordi",
  "maxBlock": "6400000",
  "lim": "100",
  "description": "Abordi is the first AbaRC-20 token",
  "logos": ["https://www.abarc20.com/abordi/abordi.png", "https://www.abordinals.com/abordi/abordi.png", "https://www.abarc20.com/abordi/abordi.mp4", "https://www.abordinals.com/abordi/abordi.mp4"],
  "links": ["https://www.abarc20.com/abordi/", "https://x.com/abordinals", "https://discord.gg/TGddbKbEp4", "https://www.abordinals.com/abordi/"]
}

Mint

Mint "amt" # of tokens of AbaRC-20 tokens of ticker "tick".

Requirements & Notes:

CHIP-7 Abordinal
NFT Royalty must be zero in order for the mint command to be valid.
CHIP-7 Name field must be the ticker ("tick", e.g. "abordi")
CHIP-7 Description must be "mint"
No license may be supplied
If "amt" is empty, then the "lim" for the ticker from the deploy command determines the number of tokens minted by the coin
If present, "amt" must be a positive integer and less than "lim"
In order to be valid, the ticker ("tick") must have been deployed in a previous block by a AbaRC-20 Deploy command and the ticker must not be minted out. If the ticker's deploy command uses maxBlock, the AbaRC-20 mint transaction must be included in a block number less than or equal to maxBlock. If the ticker's deploy command used "max", then the number of tokens minted for the ticker plus the new mint command's amt must be less than that number.

>Only one AbaRC-20 command may be issued in a Abordinal.

URI Content Outline:

{
    "p": "abarc-20",
    "op": "mint",
    "tick": "abordi", # 4-20 characters, may include unicode characters, case-insensitive
    "amt": "100" #OPTIONAL, defaults to "lim" value of the particular ticker
    "v": "1" # version, optional, default value is 1
    "t": # optional, reserved for future use
    "data": # optional, can be used for extensions
}

URI Content Example:

{
    "p": "abarc-20",
    "op": "mint",
    "tick": "abordi"
}

Transfer

To transfer a AbaRC-20 token ("mint") coin, simply transfer the NFT1 of the token coin. Similarly, standard Offers may be used to sell the coin.

To break up a AbaRC-20 token coin into coins of smaller amounts, you could trade it for AbaRC-20 NFT1's of a smaller denomination. Stay tuned for more developments in this area, and sign up for the Anarkoic e-mail list above.

Supporting Development

Donation address: xch1cchazmc92k370genxxpyuzqhtyn8m2acv46n3ue2qwnpu5s4urdqsk9fnj

Donations can be used for areas such as bounties for integration by other projects, platform utilities and future development. We suggest sending donations be sent from non-exchange addresses in case community members look to reward donators in future.

Integration

Apps Displaying AbaRC-20 should indicate if a ticker includes non-ascii characters to reduce homoglyphing risk (characters that look the same but are different). See ENS for an example. NFT sites might indicate if an NFT is a valid AbaRC-20 command NFT.

Logo accepts a URI or an nft1 id (e.g. nft1...) or coin id.

Future

We have ideas for a few innovations for the future. Sign up for our Anarkoic email newsletter above to stay informed. Expansions to the protocol will likely have a minimum block number to activate.