-
Notifications
You must be signed in to change notification settings - Fork 15
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
Use fee_per_second
from asset metadata in XCM config
#393
Comments
Hey team! Please add your planning poker estimate with Zenhub @b-yap @bogdanS98 @ebma @gianfra-t @TorstenStueber |
Hey @pendulum-chain/devs, I have doubts into which route to take to implement this, so far I see two roads: We could use the The other alternative is to replace completely the use of I don't see any other way to combine these two solutions because the actual baselines to calculate the fees are different. In terms of preference, I prefer the first option since we would still have control of the Also, both solutions would allow to control the absolute value of the fees for each token, just in different ways. |
@gianfra-t At the end both solutions are equivalent if the parameters are defined appropriately, correct? Now that we have the We could change our |
I'd also prefer the second option. I think, using the Is there a good reason not to implement it similar to what Centrifuge did, ie. using a struct that implements the By the way, @gianfra-t please don't forget to assign yourself to tickets and move them to 'in development' once you start working on them. |
Looks good to me to use the |
Thanks for your inputs! Let's go with the "second option" and adjust As for your question @ebma I think we can also use that other trader, because it behaves in the same way as |
Opening this again because we reverted the changes in #431. |
With #392 we have a
fee_per_second
attribute available for each asset. We want to use this value to replace theRelativeValue
s defined eg here.An example of an implementation that uses the
fee_per_second
attribute defined in the asset registry to derive XCM fees can be found here.The text was updated successfully, but these errors were encountered: