Version 1.6.0
If you manually create a subnet using the wizard, you are prompted to enter your token, which is then created. If you then save the genesis file from your subnet, the token is not in there.
If you wanted to recreate your subnet (like for example in development where you are testing and need a clean environment), recreating via the genesis file is very convenient. e.g
avalanche subnet create testsn --genesis path_to_genesis_file --evm --relayer --teleporter --warp
However when you do recreate it, it does't ask you to enter the token, and in fact automatically creates a TEST token. This could be handled by not ignoring the --evm-token flag and actually using it. If you do use it you get this error:
Error: specifying --genesis flag disables SubnetEVM config flags --evm-chain-id,--evm-token,--evm-defaults
So the suggestion is allow the command line to use --evm-token even when you have a genesis file.
Version 1.6.0 If you manually create a subnet using the wizard, you are prompted to enter your token, which is then created. If you then save the genesis file from your subnet, the token is not in there.
If you wanted to recreate your subnet (like for example in development where you are testing and need a clean environment), recreating via the genesis file is very convenient. e.g
avalanche subnet create testsn --genesis path_to_genesis_file --evm --relayer --teleporter --warpHowever when you do recreate it, it does't ask you to enter the token, and in fact automatically creates a TEST token. This could be handled by not ignoring the --evm-token flag and actually using it. If you do use it you get this error:Error: specifying --genesis flag disables SubnetEVM config flags --evm-chain-id,--evm-token,--evm-defaultsSo the suggestion is allow the command line to use --evm-token even when you have a genesis file.