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

Add vestedTransfer for Assets on Asset Hub #4090

Open
2 tasks done
adamsteeber opened this issue Apr 11, 2024 · 4 comments
Open
2 tasks done

Add vestedTransfer for Assets on Asset Hub #4090

adamsteeber opened this issue Apr 11, 2024 · 4 comments
Labels
I5-enhancement An additional feature request. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@adamsteeber
Copy link

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Motivation

As Asset Hub becomes more integral in the Polkadot XCM paradigm, it's important that it integrates useful defi tools. Having the right tools available will ensure that projects wanting to launch Asset Hub tokens have access to on-chain functions that facilitate tokenomics. Adding simple, out-of-the-box tools to all assets created on Asset Hub will give founders and users more flexibility in their innovations without needing to rely on trust-based, centralized solutions.

Request

While many features could be added to assets, I request that we begin with the simplest and most useful: vested transfers. Vesting is present in nearly all tokenomic models and it's quite precarious to facilitate using off-chain tools. Much like vesting.vestedTransfer on the relay chain, assets on Asset Hub could be autonomously vested on a per block basis. This simple feature will make facilitating tokenomics much easier for founders.

Solution

The core logic/framework is already fleshed out in the vesting pallet, however there could be some challenges adapting it to assets on Asset Hub. Since Asset Hub assets are customizable and don't necessarily have intrinsic value, the parameters for vested transfers may need to be dependent on an asset's existential deposit and require a DOT deposit for the on-chain storage required to facilitated vested transfers.

I could help with implementing this solution but my contractors are not briefed on Polkadot SDK pallets and I might need to contract new devs to get this done. It would probably be most cost effective if a couple of members in the fellowship work together to roll this out.

Are you willing to help with this request?

Maybe (please elaborate above)

@adamsteeber adamsteeber added the I5-enhancement An additional feature request. label Apr 11, 2024
@github-actions github-actions bot added the I10-unconfirmed Issue might be valid, but it's not yet known. label Apr 11, 2024
@acatangiu
Copy link
Contributor

I think what you are asking for is polkadot-fellows/runtimes#269 (already under way) 👍

@adamsteeber
Copy link
Author

I think what you are asking for is polkadot-fellows/runtimes#269 (already under way) 👍

That PR only handles vested transfers of DOT/KSM, not of all other assets.

@joepetrowski
Copy link
Contributor

Once we have:

Then this should be simply adding new instances of the Vesting pallet for assets.

@pandres95
Copy link
Contributor

@joepetrowski I already started working on the migration for vesting pallet to fungibles. Let you know once I have all the details and the opened issue/PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I5-enhancement An additional feature request. I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

No branches or pull requests

4 participants