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

[Assets] Allow per-account freeze / thaw for all assets with the same freezer #3451

Open
2 tasks done
JelliedOwl opened this issue Feb 22, 2024 · 0 comments
Open
2 tasks done
Labels
I5-enhancement An additional feature request. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@JelliedOwl
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

Currently, if I an issuer with multiple assets wants to freeze (or thaw) all their assets on an account, I believe they would have to call assets_freeze() for each asset in turns. And if they later add another asset, they would have to call the freeze function again for that asset for all the accounts they have previously blocked.

This would make compliance with an OFAC SDN list request (for example) a large headache for a multi-asset issuer.

Request

Is it feasible to add something like a freeze_all() function that would apply a freeze on all the assets for the same freezer account in a single call and would apply to new assets created with the same freezer address automatically? (And potentially an equivalent thaw_all() function.)

I guess it would be another list to check in addition the current freeze list when making transactions that might be frozen - I'm not sure if that's too much overhead?

If that's not a good solution, I'd welcome other suggestions, please. Or, indeed, if it's not something for the pallet itself but better in an extension.

Solution

No response

Are you willing to help with this request?

Yes!

@JelliedOwl JelliedOwl added the I5-enhancement An additional feature request. label Feb 22, 2024
@github-actions github-actions bot added the I10-unconfirmed Issue might be valid, but it's not yet known. label Feb 22, 2024
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

1 participant