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

Investigate fixed fee viability #1186

Open
ureeves opened this issue Dec 5, 2023 · 1 comment
Open

Investigate fixed fee viability #1186

ureeves opened this issue Dec 5, 2023 · 1 comment
Labels
need:feedback Call for participation: feedback is requested to fix this issue type:feature implementing a new feature

Comments

@ureeves
Copy link
Member

ureeves commented Dec 5, 2023

Summary

It might be viable to (re)introduce a fixed fee for simple transfers, for both better user experience and client-side note proliferation mitigation.

Possible solution design or implementation

A fixed fee is fairly easy to introduce, especially given the atomicity of transactions. Care should be taken to not re-introduce transaction re-execution into execute state transition (EST).

Additional context

But I still believe that having a fixed fee for transfer would be a benefit for the network. Does it worth to reintroduce it?
Originally posted by @herr-seppia in #1125 (review)

@ureeves ureeves added type:feature implementing a new feature team:Core need:feedback Call for participation: feedback is requested to fix this issue labels Dec 5, 2023
@HDauven HDauven removed the team:core label Apr 8, 2024
@HDauven
Copy link
Member

HDauven commented Apr 10, 2024

@ureeves @ZER0 @herr-seppia @miloszm Is this still relevant? Do we need to discuss this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need:feedback Call for participation: feedback is requested to fix this issue type:feature implementing a new feature
Projects
None yet
Development

No branches or pull requests

2 participants