CIP113 Specs

[jinglescode]

1. create tokens policy
   1. create new tokenization policy, user will define:
      1. token name
      2. token symbol
      3. decimals
      4. metadata
      5. freezeable (yes/no)
   2. via SDK (createToken({})), same parameters as above
      const tokenId = await wallet.createToken({
      tokenName: "My Token",
      tokenTicker: "MTK",
      decimals: 8,
      isFreezable: true,
      metadata: "",
      });
   3. a new tokenization policy will require a MeshWallet, this wallet is for the developer, this wallet is the issuer wallet. when init the package, require a MeshWallet
2. minting
   1. mint via SDK const txId = await mintTokens(123), where 123 is the amount to mint
      1. minted tokens will be inside issuer wallet
      2. minting requires the issuer wallet (MeshWallet) and perform signing
3. query
   1. show balance in wallet
      1. get issuer's own token balance (const balance = await getTokenBalance()
      2. get wallet address's token balance const balance = await getTokenBalance('address'))
   2. show token metadata (const metadata = await getTokenMetadata())
      1. token name
      2. token symbol
      3. metadata
4. transfer tokens
   1. transfer via SDK const txId = await transferTokens({ receiverAddress: 'address', tokenAmount: 123 })
   2. batch transfer via SDK batchTransferTokens([{ receiverAddress: 'address1', tokenAmount: 123 }, { receiverAddress: 'address2', tokenAmount: 456 }])
   3. transfer requires will require the issuer wallet (MeshWallet) and perform signing
5. freeze, unfreeze and burn
   1. freeze (const txId = await freezeTokens('address'))
   2. burn (const txId = await burnTokens(123))
   3. unfreeze (const txId = await unfreezeTokens('address'))
   4. these require wallet signing

[ruhil6789]

@Temasar1 I would like to contribute to this issue, as I am already actively working on CIP-113 programmable tokens.