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

Vesting should not fund extrinsic inclusion fees #4200

Closed
bedeho opened this issue Aug 23, 2022 · 1 comment
Closed

Vesting should not fund extrinsic inclusion fees #4200

bedeho opened this issue Aug 23, 2022 · 1 comment
Assignees
Labels

Comments

@bedeho
Copy link
Member

bedeho commented Aug 23, 2022

In the interest of simplifying the relevance of locks being able to pay for various costs associated with transactions, which ideally should not be the invite lock, we need to remove the ability of having funds subject to vesting constraint be able to fund extrinsic inclusion fees. Currently this is the functionality of the vesting pallet we use, which comes with the FRAME suite.

We have two alternatives

  1. forking vesting pallet and making lock configurable: we likely could get this merged back into upstream even, but lets not depend on that!
  2. use alternative vesting pallets, e.g. from orml

┆Issue is synchronized with this Asana task by Unito

@bedeho
Copy link
Member Author

bedeho commented Aug 24, 2022

We are going with 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants