Automatically setup native token on quickstart local networks #555
Comments
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
and others
What problem does your feature solve?
It's not intuitive that on the local network that the native asset has not been setup with a contract.
On pubnet, testnet, and futurenet the native asset contract is created. It's very easy to get used to that and to just start using it.
On the local network the developer has to create it themselves with:
I've forgotten several times to create it and it just chews times debugging then realizing and running the command.
What would you like to see?
The native asset contract deployed automatically on quickstart when running the local network, so it's just good to go.
What alternatives are there?
Do nothing. Remind people to create it.
The text was updated successfully, but these errors were encountered: