it is important in some cases to know how many tokens exist
the total issued can be returned if that is easier than current unburned supply
the usecase is to fit microtoken count in 64 bits. for SC shares that only have 676 this is not a problem but if an asset has over 18 trillion tokens then the microtoken supply for it would overflow 64 bits.
Since there is no need to make a microtoken out of such a large supply asset, we can just return an error if the user tries to make a microtoken out of an asset that could overflow 64 bits.
Currently this is not possible so we need to restrict microtokenization to SC shares, even though it would be quite useful for expensive tokens in general
it is important in some cases to know how many tokens exist the total issued can be returned if that is easier than current unburned supply
the usecase is to fit microtoken count in 64 bits. for SC shares that only have 676 this is not a problem but if an asset has over 18 trillion tokens then the microtoken supply for it would overflow 64 bits.
Since there is no need to make a microtoken out of such a large supply asset, we can just return an error if the user tries to make a microtoken out of an asset that could overflow 64 bits.
Currently this is not possible so we need to restrict microtokenization to SC shares, even though it would be quite useful for expensive tokens in general