Spend proposal templates should use human readable amounts

[JakeHartnell]

Going through things, really think we should just use human readable amounts everywhere. Otherwise it's confusing to explain to a user that 1 ujunox is equal to 0.0000001 JUNOX.

[0xekez]

I believe that this is currently controlled by what the NEXT_PUBLIC_STAKING_DENOM environment variable is set to. For example, setting:

NEXT_PUBLIC_STAKING_DENOM="junox"

Results in spend proposals that use junox:

@JakeHartnell - I'm unfamiliar with the whole codebase so possible it would break other things - would changing that environment variable in the .env file fix this issue?

[JakeHartnell]

I believe that this is currently controlled by what the NEXT_PUBLIC_STAKING_DENOM environment variable is set to. For example, setting:

NEXT_PUBLIC_STAKING_DENOM="junox"

Results in spend proposals that use junox:

@JakeHartnell - I'm unfamiliar with the whole codebase so possible it would break other things - would changing that environment variable in the .env file fix this issue?

This won't work. : )

Chain / contracts expect the amounts in the micro unit.

[0xekez]

Chain / contracts expect the amounts in the micro unit.

Learn something new every day :) Am I correct in understanding then that the goal of this is to have the user input amounts in juno and then have the ui convert / use ujuno under the hood?

[JakeHartnell]

Chain / contracts expect the amounts in the micro unit.

Learn something new every day :) Am I correct in understanding then that the goal of this is to have the user input amounts in juno and then have the ui convert / use ujuno under the hood?

Yes!