IPX Coin Standard

An extension to Sui Network's Coin. Coins created via the IPX Coin Standard can be minted, burnt and updated with different capabilities.

Problem

Coins created via Sui Network Coin have all the rights associated with one capability, the TreasuryCap.

The holder of the TreasuryCap can mint, burn and update the Coin. This design is quite limiting because all the rights are associated with a single capability.

What happens if a user wants to ensure that its coin can be burnt but not mintable? He would have to write its own contract.

Most users choose to simply send the TreasuryCap to the systems address, the famous 0x0, because no one has access to it. Therefore it is considered burnt. However, since no one has access to the TreasuryCap, no one can burn the coin nor update its icon, description, symbol or name. There are cases in which coins need to update its metadata due to a rebrand or broken uris.

Solution

The IPX Coin Standard separates the three rights of the TreasuryCap into three separate capabilities: Burn, Mint and Update metadata. This flexible design means that a user can make his/her coin burnable while preventing coins to be minted forever.

• MintCap allows the holder to mint coins

• BurnCap allows the holder to burn coins

• MetadataCap allows the holder to update the coin name, description, icon uri and symbol

The deployer can choose to make the coin burnable by anyone who has coins in his/her wallet.

At deployment the user can choose to make the coin mintable, burnable and/or updateable and decide who has those rights. The code is open source on Github and immutable. Not even the IPX team can change the standard making it safe to use.

Package Address: 0x644c3b903a9636eba77e56cefd7c207734fb80dbf9a16af10f33ce03cbb65670