-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
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
Standard or minimum transaction fee #230
Labels
kind/new-feature
Propose the addition of a new feature that does not yet exist
Milestone
Comments
kwunyeung
added
the
kind/new-feature
Propose the addition of a new feature that does not yet exist
label
Jul 16, 2020
@kwunyeung Yes, this can be easily achieved using the Do we have any idea on the min fee to be paid for each message? |
RiccardoM
added
the
status/specification
This feature is currently in the specification process
label
Jul 16, 2020
We can keep the current testing amount |
RiccardoM
removed
the
status/specification
This feature is currently in the specification process
label
Oct 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature description
Be default,
Cosmos-SDK
let full nodes to define theirmin-gas-prices
. This would lead toDesmos
have a chance of facing zero-fee spam attack. I think we have to setup a minimum or standard fee structure for differentPosts
andReports
message types. We should not let users be able to post, make reactions or report without any fee. We can keep the way how otherStdTx
is working but only keeps transactions inPosts
andReports
module have such constraints.IRISnet has a standard minimum fee and e-Money has a PoA configurable minimum fee. I think we can learn how they are doing. While we are still studying the tokenomics and usage of a secondary fee token, we can first test this mechanism with the testing
udaric
. There is a module basedAnteDecorator
in the SDK for customizing theAnteHandler
. Can this be achieved by making use of it?The text was updated successfully, but these errors were encountered: