Another common topic...
how to best handle and explain GAS in Ethereum?!
I'm of the opinion that, if possible, gas should be hidden from the user,
and if in that particular moment in time the average gas fees in the network are high, then you should resort to minimizing the cognitive effort of the user (who won't know what gas is nor, by consequence, what a good gas price actually is), by using proxies, such as:
time estimates for the processing of the transaction
- gas price in FIAT, $ or other
- suggest default ranges
Some thoughts about teaching the user what the "expert's choice" would be are written in the Web3 Design Principles.
Also, Matt Condon in the Telegram was pointing to a research of possible variations on gas
created by someone at IDEO CoLab
check it out, it has interesting alternatives