Expiry and tokenKeys of IHederaTokenService.HederaToken

[daniel-rekursive]

HederaTokenService.createFungibleToken() function accepts IHederaTokenService.HederaToken as its first arg.

struct HederaToken {
  // The publicly visible name of the token. The token name is specified as a Unicode string.
  // Its UTF-8 encoding cannot exceed 100 bytes, and cannot contain the 0 byte (NUL).
  string name;
  // The publicly visible token symbol. The token symbol is specified as a Unicode string.
  // Its UTF-8 encoding cannot exceed 100 bytes, and cannot contain the 0 byte (NUL).
  string symbol;
  // The ID of the account which will act as a treasury for the token as a solidity address.
  // This account will receive the specified initial supply or the newly minted NFTs in
  // the case for NON_FUNGIBLE_UNIQUE Type
  address treasury;
  // The memo associated with the token (UTF-8 encoding max 100 bytes)
  string memo;
  // IWA compatibility. Specified the token supply type. Defaults to INFINITE
  bool tokenSupplyType;
  // IWA Compatibility. Depends on TokenSupplyType. For tokens of type FUNGIBLE_COMMON - the
  // maximum number of tokens that can be in circulation. For tokens of type NON_FUNGIBLE_UNIQUE -
  // the maximum number of NFTs (serial numbers) that can be minted. This field can never be changed!
  uint32 maxSupply;
  // The default Freeze status (frozen or unfrozen) of Hedera accounts relative to this token. If
  // true, an account must be unfrozen before it can receive the token
  bool freezeDefault;
  // list of keys to set to the token
  TokenKey[] tokenKeys;
  // expiry properties of a Hedera token - second, autoRenewAccount, autoRenewPeriod
  Expiry expiry;
}

• What value should tokenKeys and expiry be? Any detailed doc describing them?
• Is it okay to call HederaTokenService.createFungibleToken(token, initialTotalSupply, decimals) where token.tokenKeys and token.expiry are empty?

Example code here doesn't give me clear understanding of what those values are and what it should accept.
https://github.com/hashgraph/hedera-smart-contracts/blob/main/hts-precompile/TokenCreateContract.sol#L44-L46

[daniel-rekursive]

cc @shemnon @SimiHunjan @dimitar-dinev
Thanks

[stoqnkpL]

Hey @daniel-rekursive,

TokenKey and Expiry are struct types defined in IHederaTokenService. We have an open PR with updates to HIP-358 that provide detailed explanations of all new structs and how to use them as arguments when creating tokens. Please take a look at the description of different fields that's provided there, hopefully it would make things clearer!
As for your second question, the rule of thumb is that the same restrictions and requirements for token creation apply when creating a token through the precompile as would apply if the same token is created through HTS HAPI.

[daniel-rekursive]

For the second question, does it mean it's okay to leave token.tokenKeys and token.expiry without assigning any value?
@stoqnkpL

[stoqnkpL]

Hey @daniel-rekursive,
It is okay to leave tokenKeys empty, but keep in mind that a token without an admin key is immutable and cannot be updated.
For the expiry there are two valid options:

1. Auto renew account is provided and the auto renew period is valid
2. The second that was passed (IHederaTokenService.Expiry.second) is in the future compared to token creation time

All other cases would result in either INVALID_RENEWAL_PERIOD or INVALID_EXPIRATION_TIME status and token creation will fail.

[daniel-rekursive]

token without an admin key is immutable and cannot be updated

@stoqnkpL What do you mean it is "immutable" and "cannot be updated"?

[stoqnkpL]

Usually, HTS Tokens can be updated, for example, the token name, symbol, treasury account, or other token properties can be changed on an existing token. In order to be able to execute a token update, however, you would need to sign the transaction with the token admin key. If the token has no admin key, this means it can never be updated or deleted.

[stoqnkpL]

Hey Daniel, Sorry for the delayed response. Is this issue still relevant? I'm trying to reproduce it, can you share a bit more context, how are you constructing the arguments for createFungileToken()?

…

On Mon, May 16, 2022 at 7:58 PM daniel-rekursive ***@***.***> wrote: I am getting INSUFFICIENT_TX_FEE error when calling createFungibleToken() The tx was initiated via ContractExecuteTransaction.setGas(5000000) and setPayableAmount(100) Why am I getting this error? @stoqnkpL <https://github.com/stoqnkpL> Thanks — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUKIS65HJC5XS5JSIZHWDZDVKJ5BPANCNFSM5UWZK2OA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Kalina-Todorova]

Hi @daniel-rekursive is this still an issue for you?

[Nana-EC]

@daniel-rekursive did you receive the information you needed.
Notably this should be a discussion item so i'll be converting this over