We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this related to
10:53AM DBG minted coins from module account amount=3984456stake from=mint module=x/bank 10:53AM INF updated the fee market module=x/feemarket params={"alpha":"0.000000000000000000","beta":"1.000000000000000000","delta":"0.000000000000000000","enabled":true,"fee_denom":"stake","gamma":"0.000000000000000000","max_block_utilization":30000000,"max_learning_rate":"0.125000000000000000","min_base_gas_price":"1.000000000000000000","min_learning_rate":"0.125000000000000000","window":1} 10:53AM INF updated the fee market average_block_utilization=0.000000000000000000 height=1 module=x/feemarket net_block_utilization=-15000000 new_base_gas_price=1.000000000000000000 new_learning_rate=0.125000000000000000 10:53AM DBG Pruned proposal 1 module=x/group 10:53AM DBG Pruned proposal 2 module=x/group 10:53AM DBG Pruned proposal 3 module=x/group 10:53AM DBG hash of all writes workingHash=E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 Simulating... block 1/200, operation 0/0.--- FAIL: BenchmarkSimulation simulate.go:337: error on block 1/200, operation (0/83) from x/staking: got length 0: no fee coin provided. Must provide one. [skip-mev/[email protected]/x/feemarket/ante/fee.go:106] Comment: unable to deliver tx FAIL exit status 1
Or, is it that we should be explicitly setting a denom in chain config?
thanks!
The text was updated successfully, but these errors were encountered:
we've found it :)
Sorry, something went wrong.
No branches or pull requests
Is this related to
Or, is it that we should be explicitly setting a denom in chain config?
thanks!
The text was updated successfully, but these errors were encountered: