Skip to content
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

Closed
kwunyeung opened this issue Jul 16, 2020 · 2 comments · Fixed by #314
Closed

Standard or minimum transaction fee #230

kwunyeung opened this issue Jul 16, 2020 · 2 comments · Fixed by #314
Assignees
Labels
kind/new-feature Propose the addition of a new feature that does not yet exist
Milestone

Comments

@kwunyeung
Copy link
Contributor

Feature description

Be default, Cosmos-SDK let full nodes to define their min-gas-prices. This would lead to Desmos have a chance of facing zero-fee spam attack. I think we have to setup a minimum or standard fee structure for different Posts and Reports message types. We should not let users be able to post, make reactions or report without any fee. We can keep the way how other StdTx is working but only keeps transactions in Posts and Reports 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 based AnteDecorator in the SDK for customizing the AnteHandler. Can this be achieved by making use of it?

@kwunyeung kwunyeung added the kind/new-feature Propose the addition of a new feature that does not yet exist label Jul 16, 2020
@RiccardoM
Copy link
Contributor

@kwunyeung Yes, this can be easily achieved using the AnteDecorator and making sure that a min fee is included if the transaction contains one of the above mentioned message types.

Do we have any idea on the min fee to be paid for each message?

@RiccardoM RiccardoM added the status/specification This feature is currently in the specification process label Jul 16, 2020
@kwunyeung
Copy link
Contributor Author

We can keep the current testing amount 0.01 Daric first.

@RiccardoM RiccardoM removed the status/specification This feature is currently in the specification process label Oct 8, 2020
@RiccardoM RiccardoM added this to the v0.14.0 milestone Oct 14, 2020
@leobragaz leobragaz self-assigned this Oct 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/new-feature Propose the addition of a new feature that does not yet exist
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants