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

ETH fees in withdraw function #328

Open
PaulRBerg opened this issue Nov 6, 2024 Discussed in #327 · 2 comments
Open

ETH fees in withdraw function #328

PaulRBerg opened this issue Nov 6, 2024 Discussed in #327 · 2 comments
Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.

Comments

@PaulRBerg
Copy link
Member

The design should be the same as in Lockup.

Discussed in #327

Originally posted by PaulRBerg November 6, 2024
We've recently decided to charge ETH fees instead of protocol fees in Lockup. ETH fees make much more sense for Lockup streams per all the reasons provided here.

Now, for Flow streams, the fee is paid in stablecoin. This is not bad, but I wonder if charging in ETH wouldn't be better?

  1. More consistency across our fee models
  2. Less psychological resistance; the user has to pay a fee in ETH anyway (for the gas), so charging $1 in ETH should feel less pressuring than paying a separate fee in USDC (from the recipient's salary)
  3. Charging in ETH means that we are charging the account that withdraws, not the recipient (these accounts might not be the same)

Notes:

  • I'm not suggesting to change the implementation now because doing so would cancel the validity of the security audits.
  • We will start charging in ~March anyway, so changing the implementation in Flow now would be overkill.

Cc @sablier-labs/everybody for feedback.

@PaulRBerg PaulRBerg added priority: 1 This is important. It should be dealt with shortly. effort: medium Default level of effort. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear. labels Nov 6, 2024
@smol-ninja
Copy link
Member

Great idea. Does this also mean removing existing implementation of protocol fee?

@PaulRBerg
Copy link
Member Author

Thank you.

TBD if we remove the protocol fees. We should carefully listen to user feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: medium Default level of effort. priority: 1 This is important. It should be dealt with shortly. type: feature New feature or request. work: clear Sense-categorize-respond. The relationship between cause and effect is clear.
Projects
None yet
Development

No branches or pull requests

2 participants